|
|
|
|
#1
08-09-2012, 12:26 PM
|
|||
|
|||
|
After removing the issue with the interop DLL that was part of source control this is the behavoir I observed.
I am NOT saying this is dependant on x64 or x86, all I am saying here is that if I had the x64 bit version of VB installed on Win7 x64 then I didnt see the issue, if I used the x86 version of VB on Win7 x64 then I saw VS hang and crash. Not sure if it has to do with VS trying to create the interop DLL or what. I was hoping you could help interpret these results. 
|
|
#3
08-09-2012, 01:46 PM
|
|||
|
|||
|
I was able to add the refrence as descibed above, I will continue testing. Since you confirmed the new framworks, I will try 4.0 to avoid the source control deployment issue I had.
It will take a few days, but I will post my findings on this thread.
|
|
#4
08-14-2012, 03:12 PM
|
|||
|
|||
|
So far so good, I created the new custom action, its targeting the 4.0 frameowok and things are running as expected.
Thanks for the help!
|
 |
|
|
Hybrid Mode
