Please keep me updated on your progress with this. In theory this should get around the issue until we can officially fix it in Test Studio. config file your executable you should be able to force it to load from somewhere other than the GAC per this documentation and this documentation. There is a way to configure an application to look for a required DLL in an alternate location. In the meantime one of our developers suggested a workaround you may be able to implement yourself. To remove this assembly from the GAC, use the command gacutil /u SomeAssembly For this you only need the assembly name. thus you will not have to wait until our next official public release many weeks away. gacutil /i C:someFolderSomeAssembly.dll Note that the full path must be used so that the tool grabs the correct assembly. Also once we have a fix in place we'll can create a private build just for you and send it to you. gacutil /i yourdll.dll You find the Visual Studio Command Prompt in the start menu under Programs -> Visual Studio -> Visual Studio Tools. They have agreed to work on it as a high priority as soon as Service Pack 2 goes live. We don't have time to include the fix for this in that service pack. The bad news is that we're in the middle of finishing our Service Pack 2 release. First it is high on their priority list to fix (i.e. I heard back from our development team about this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |