Came across this interesting post on the changes in the NCL.
http://blogs.msdn.com/ncl/archive/2009/07/20/new-ncl-features-in-net-4-0-beta-2.aspx
Tuesday, July 21, 2009
Friday, July 17, 2009
DLL HELL
Faced DLL hell issues after a real long time.
In the dev env, we compiled the VB6 dll and tested it and it worked fine.
But the minute we put it in test, it started off giving the CLSID errors.
We then registered, unregistered quite a few times. Turned out that there were multiple registrations of the same DLL. So we uninstalled all the versions, took the latest from VSS, compiled the DLL again, regsitered it and it finally worked.
Took around 2 whole days for it!!
In the dev env, we compiled the VB6 dll and tested it and it worked fine.
But the minute we put it in test, it started off giving the CLSID errors.
We then registered, unregistered quite a few times. Turned out that there were multiple registrations of the same DLL. So we uninstalled all the versions, took the latest from VSS, compiled the DLL again, regsitered it and it finally worked.
Took around 2 whole days for it!!
Monday, July 13, 2009
Tuesday, June 30, 2009
Not a valid assembly (Add Reference failure)
When trying to add a reference to a VB DLL, you may receive the following error popup: A reference to
'assemblyname.exe' could not be added. This is not a valid assembly or COM
component. Please make sure that the file is accessible, and that it is a
valid assembly or COM component.
WorkAround:-
There were some on the net, but I registered the DLL using regsvr and added it from the COM components tab and it worked fine.
'assemblyname.exe' could not be added. This is not a valid assembly or COM
component. Please make sure that the file is accessible, and that it is a
valid assembly or COM component.
WorkAround:-
There were some on the net, but I registered the DLL using regsvr and added it from the COM components tab and it worked fine.
Subscribe to:
Posts (Atom)