This project has moved and is read-only. For the latest updates, please go here.


Current code does not correctly install the Custom Tool


When we checked out the code of today, built the vsxi on one machine (with VS 2010 Premium), then install that on another machine with the same version of VS, the custom tool can not get startet, saying something like "The custom tool 'CsdFileGenerator' can not be found".
The issue is gone, once the code gets copied and built on the second machine.
Closed Jul 14, 2011 at 12:11 AM by andym1978
A few confirmed successful installations and no further bug reports. Closing for now.


andym1978 wrote Jun 30, 2011 at 8:27 PM

Some changes have been made to the VSIX since this was reported. They MAY have fixed this issue, but I will need to try and reproduce this behavior on a clean machine.

wrote Jul 1, 2011 at 10:37 AM

wrote Jul 5, 2011 at 4:06 PM

bugkiller wrote Jul 5, 2011 at 5:03 PM

In the extension package ConfigurationSectionDesigner.DslPackage.pkgdef file one of the registry keys was pointing not to "CodeBase"="$PackageFolder$\ConfigurationSectionDesigner.Dsl.dll" but rather to some private build location so the assembly was not able to be located by the runtime. After making changes directly in the package everything seems ok. Unfortunately I did not find place where the .pkgdef file is stored (maybe it get generated during build process so I was not able to upload patch). Please make appropriate changes.

andym1978 wrote Jul 5, 2011 at 9:46 PM

I believe this may be caused by a VS2010 bug (that is over a year old!). I'm hoping to find a workaround that isn't as ugly as the ones I've seen online. More info can be found at the following link:

wrote Jul 6, 2011 at 5:52 PM

andym1978 wrote Jul 6, 2011 at 5:52 PM

I think I have resolved the issue, but it wasn't easy, nor was it entirely pretty. I installed the "MSBuild.Community.Tasks" library and added a regex text replace task that fixes the offending entry in the pkgdef file before the VSIX is built. I need to add some comments about this for the other developers before uploading source code, but will include the build with this fix in this post. I can't confirm that it works at the moment, so if you have a moment to try it out, I would appreciate it. Thanks.

andym1978 wrote Jul 7, 2011 at 12:42 AM

I made a slight tweak to the VSIX after my test failed on a clean developer box. The 2.0.0 r2 download (in the downloads section) is working as expected and should eliminate this issue (finally!).

wrote Jul 7, 2011 at 12:43 AM

bugkiller wrote Jul 7, 2011 at 7:57 AM

Thanks a lot for the fix. I confirm that on clean install the designer now works with no issues. At least for me.

andym1978 wrote Jul 7, 2011 at 3:51 PM

Excellent news! That was a pretty important issue to get out of the way.

I have uploaded the source to the fix in source code change set 60330.

wrote Jul 7, 2011 at 3:52 PM

wrote Jul 14, 2011 at 12:09 AM

wrote Jul 14, 2011 at 12:11 AM

wrote Jul 14, 2011 at 12:11 AM

wrote Feb 22, 2013 at 12:30 AM

wrote May 16, 2013 at 12:04 PM