|
|
|
|
#1
08-08-2012, 10:43 AM
|
|||
|
|||
|
Custom Action VB 8.1
I am working on updating a custom action I have writen to use VB 8.1. If I removed the old refrence to VB7.1 and update it to point to C:\Program Files (x86)\VisBuildPro8\System\VisBuildSrv.dll it causes VS2010 to crash. The solution is ment to target the 2.0 framework, should that be updated to 4.0? Should I be refrencing the Interop.dll directly? Please advise
|
|
#2
08-08-2012, 10:47 AM
|
|||
|
|||
|
Here is the error log that gets generated:
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73 Faulting module name: VisBuildSvr.dll_unloaded, version: 0.0.0.0, time stamp: 0x5018920b Exception code: 0xc0000005 Fault offset: 0x37de81c0 Faulting process id: 0x6cc Faulting application start time: 0x01cd7579abbb3931 Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe Faulting module path: VisBuildSvr.dll Report Id: 95dd64a5-e16e-11e1-8a13-0800277c2dd2
|
|
#3
08-08-2012, 11:12 AM
|
|||
|
|||
|
I wasn't able to reproduce that behavior. Maybe try restarting VS and make sure you have SP1 installed. Are you able to open Samples\User Actions\NETAction\NETAction.sln from the VBP install, which references the v8 interop DLL? One option might be to manually copy the reference from NetAction.csproj after upgrading the project. If you add a reference to VisBuildSvr.dll, it will actually reference the interop DLL (creating if necessary), or you can add the interop DLL reference directly. You should be able to target either .NET 2.0 or 4.0.
|
|
#4
08-08-2012, 12:49 PM
|
|||
|
|||
|
The error still occurs not sure what to do here!
In a previouse post, you said that its best to target 2.0, with the 8.1 is it safe to target the 4.0 framework? See refrence below: http://www.kinook.com/Forum/showthread.php?t=4987 If 4.0 is supported I can try doing that and see if it handles interop's differntly.
|
|
#5
08-08-2012, 01:11 PM
|
|||
|
|||
|
Oh yeah, forgot about that. Nothing has changed in v8.1 regarding custom actions, so 2.0 is probably still the best choice. Are you able to open Samples\User Actions\NETAction\NETAction.sln from the VBP install, which references the v8 interop DLL? Did you try manually copying the VisBuildSvr reference from NetAction.csproj after upgrading the project?
|
|
#6
08-08-2012, 01:16 PM
|
|||
|
|||
|
I tried opening that but htere was no solution file just a project file and it upgraded the solution to VS2010. There was an interop DLL in a bin directory already so that refrence was just pointing to that and not the one in the VB 8 install directory. I could just copy the DLL to my project but I wasnt sure if that was approprate.
VS2010 doesnt handle interop DLL well when it comes to deployment packages anyway, it ignors these files. 4.0 doesnt require them the same way that older framworks do. Just to try it I will upgrade my project to 4.0 to see what that does, I will let you know the results. Do you know when 4.0 will be officially supported?
|
|
#7
08-08-2012, 01:37 PM
|
|||
|
|||
|
Still getting errors, not sure what to try next. I even resorted back to verion 8 but that didnt work either, still get the error from VS2010 below:
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73 Faulting module name: VisBuildSvr.dll_unloaded, version: 0.0.0.0, time stamp: 0x4f8ad884 Exception code: 0xc0000005 Fault offset: 0x37de7090 Faulting process id: 0xb10 Faulting application start time: 0x01cd75939b369cc9 Faulting application path: c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe Faulting module path: VisBuildSvr.dll Report Id: 694cb18a-e187-11e1-9bb6-0800277c2dd2
|
 |
|
|
Hybrid Mode
