I don’t remember maps taking so long to load in BT2004. It seems like starting with 2006 and now in R2, I try to open a map, and I watch the CPU go crazy, sometimes for 30-60 seconds before the map appears on the screen. I’ve been running on Virtual PC or VM since using 2006, could that alone be an issue?
I do all my dev work directly on my laptop. Even there, I have seen some slowness and even VS crashing. Usually with larger maps and schema. For some reason, they still don’t have them working very well in VS.
I also have issues if I have VS open and restart the Hosts / SQL / SSO. It’s a 75% chance of a crash. Don’t get that one either.
Another one that bombs on me almost every time is when I try to connect a scripting functoid to an external C# assembly. It usually crashes Visual Studio the first time, then after VS comes back, it works fine.
The larger your schemas are, the longer your maps will take to load. Working on a VM can exacerbate the issue. Tip: don’t leave a bunch of maps open when you close VS. Otherwise, you will be stuck waiting for it to load all of the maps the next time you open your solution. I have seen the issue with VS crashing when using external assemblies from maps too. Never found a good way to fix it though.
Author
Posts
Viewing 1 reply thread
The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.