Last week I gave a presentation internally at our Info Support Knowledge Transfer evenings. Based on a deep dive training I got to attend on Campus begin of May, I presented a session on Windows Workflow 4.0. As you might know I am passionate about two technologies that I try to dig into as deep a s possible and those are visual Studio Team System and Windows Workflow Foundation. During the preparation of my talk on workflow, I obviously wanted to show some workflow designs and create some designs on the fly.
But Every time I wanted to create a new Workflow, the designer crashed and Visual Studio got closed 🙁
It took me some while to discover that the crash was caused by the Visual Basic expression editor that gets activated once you create a workflow. This editor was unable to load a required assembly. It appears that this was caused by the fact that I installed Visual Studio at a different location then the default c:\ drive.
In the Beta the bits don’t check the install directory location in the registry but just assume this to be the default location.
But how could I fix this? I did install on D:\ and was not willing to install again, since that would take a lot of time.
After some digging around I found a great solution that is posted at the connect site. You can create a symbolic link at the OS level on the file system.
When you make a c:\profgram Files\Visual Studio 10.0 directory point to the actual installation on the D:\ drive the issue is solved.
You can use the mklink command for that and specify the /J option to create a directory junction. After running mklink as an administrator and restarting Visual Studio , I was able to create workflows.
Hope this helps if you run into the same issue.
CTO at Xpirit, Microsoft Regional Director, Visual studio ALM MVP, Speaker, Pluralsight Author and IT Architect Consultant