I'm getting the above error when choosing "Run custom tool" on a razor file; when I just save, nothing happens.
In Visual Studio's Error List, I get the following:
"Custom tool error: Could not load file or assembly 'file:///C:\Users\john\AppData\Local\assembly\dl3\MH40ZN5E.14X\44VHO17O.KV9\f801bc8b\bb84bb72_a7abcd01\RazorGenerator.Core.v1.dll' or one of its dependencies. The system cannot find the file specified."
The "bb84bb72_a7abcd01" folder mentioned doesn't exist.
I have verified that the project is running MVC 3 and WebPages 1.
I have uninstalled and reinstalled both the Nuget package and the VS extension.
I have run devenv.exe /log but no error messages in the log file (but I'm attaching it anyway).
It still works fine in VS2010 on the same project.
Any ideas?
Comments: Hi David, Its been a bit of a hassle but I have managed to create a shareable solution that reproduces the issue reliably on my machine. Download the source sln from me via Drive (File>Download): https://docs.google.com/file/d/0B4imppDe7R0Gcm5MbnJITFVoT0k/edit?usp=sharing Its a super simple hybrid webforms/mvc app using razorgenerator to embed the mvc stuff into webforms. To reproduce the issue: If you run the myapp.com project you can see the default page is webforms,(/default.aspx) and there is a link to the mvc controller & view page embeded via razor generator at /home/index which all works because the index view is already generated. Now un-install the razorgenerator vsix using VS and restart studio. Now install the razorgenerator vsix using VS and restart studio. Now open the app, right click in solution explorer on "MyApp.MVC\Views\Home\index.cshtml" and select Run Custom Tool to receive the not implemented error. RazorGenerator is then broken and will not regen any views. The only way to then manually fix the sln/studio is to copy the dlls from the appropriate extensions folder C:\Users\[0000]\AppData\Local\Microsoft\VisualStudio\11.0\Extensions\.........\v2\ to the appropriate assembly cache folder C:\Users\[0000]\AppData\Local\assembly\dl3\............... I really hope this is enough for you to repro the issue!
In Visual Studio's Error List, I get the following:
"Custom tool error: Could not load file or assembly 'file:///C:\Users\john\AppData\Local\assembly\dl3\MH40ZN5E.14X\44VHO17O.KV9\f801bc8b\bb84bb72_a7abcd01\RazorGenerator.Core.v1.dll' or one of its dependencies. The system cannot find the file specified."
The "bb84bb72_a7abcd01" folder mentioned doesn't exist.
I have verified that the project is running MVC 3 and WebPages 1.
I have uninstalled and reinstalled both the Nuget package and the VS extension.
I have run devenv.exe /log but no error messages in the log file (but I'm attaching it anyway).
It still works fine in VS2010 on the same project.
Any ideas?
Comments: Hi David, Its been a bit of a hassle but I have managed to create a shareable solution that reproduces the issue reliably on my machine. Download the source sln from me via Drive (File>Download): https://docs.google.com/file/d/0B4imppDe7R0Gcm5MbnJITFVoT0k/edit?usp=sharing Its a super simple hybrid webforms/mvc app using razorgenerator to embed the mvc stuff into webforms. To reproduce the issue: If you run the myapp.com project you can see the default page is webforms,(/default.aspx) and there is a link to the mvc controller & view page embeded via razor generator at /home/index which all works because the index view is already generated. Now un-install the razorgenerator vsix using VS and restart studio. Now install the razorgenerator vsix using VS and restart studio. Now open the app, right click in solution explorer on "MyApp.MVC\Views\Home\index.cshtml" and select Run Custom Tool to receive the not implemented error. RazorGenerator is then broken and will not regen any views. The only way to then manually fix the sln/studio is to copy the dlls from the appropriate extensions folder C:\Users\[0000]\AppData\Local\Microsoft\VisualStudio\11.0\Extensions\.........\v2\ to the appropriate assembly cache folder C:\Users\[0000]\AppData\Local\assembly\dl3\............... I really hope this is enough for you to repro the issue!