VisualStudio MDG integration 3.0 failing

[danm]

Hello,
 I'm using 7.0/818 and VS integration 3.0. When I synchronize a package, it brings up a bunch of files ready for import. I choose Both (forward and reverse sync, or just reverse syn, it doesn't matter), and select all of the files. The tools runs, a dialog pops too quickly to read, and it finishes. However nothing is imported into the model.

  I've tried several things, creating new models, rebooting, etc, but no go. Has anybody else seen such behavior?

Dan

[«Midnight»]

Hey Dan,

I remember some hair pulling - and I have precious little remaining hair for that - when I did an evaluation of an earlier version. It was some time ago so I don't remember whether I had exactly the same problem as you.

I eventually got it solved. I needed to build the project on the VS side to make transfers work both ways. In fact, I think they didn't work at all in one direction until I did a build.

Play around with it a bit and please let me know what you learn. My earlier evaluation was cut short by other priorities, but I am about to get into this again. I'd hate to burn all that learning curve time again.

David

[danm]

It's worked great so far, then yesterday - poof - it decided to stop. It's picking up the files to import as I said, it's just decided not to put them in the model.

Building or not doesn't make any difference. I just created a new workspace and it didn't fix anything. VS is using Team Foundation Server, what else can I do to find the problem? Grrr, I'm stuck ...

[danm]

Stop the presses! I cleared out my workspaces, and created a brand new one. I tried this once earlier, but it still failed. Now it works again.

Odd. There seemed to be something off with my workspace that it didn't like, but at least I'm back up and running.

[«Midnight»]

Dan,

Do you by any chance have a copy of the old - non-functional - workspace?

If so, please file a bug report with Sparx, and include the workspace. They should be very interested in any configuration that causes the product to fail.

David

[danm]

No unfortunately it's company IP which I can't send outside. My recommendation to Sparx is to improve the error reporting, or the reporting in general to make it possible to catch the problem if it occurs again.