.NET Deployment Errors
-
OK. I am confused. I thought deployment was suppose to be easier. I have a VB.NET app that uses 3rd party DLL's to display a map on the UI and create routes for fleet tracking. The data is loaded from a web service that uses SOAP to return XML data points that are used to map the routes. I am getting DLL registration errors on the client's PC when they try to install the app. I used the VS.NET template to create the msi. What gives??? :confused: I should add that the target system had the SOAP SDK and the .NET framework installed on it prior to the app being installed. Any ideas why the install is getting errors? I thought .NET was not suppose to register DLL's.
-
OK. I am confused. I thought deployment was suppose to be easier. I have a VB.NET app that uses 3rd party DLL's to display a map on the UI and create routes for fleet tracking. The data is loaded from a web service that uses SOAP to return XML data points that are used to map the routes. I am getting DLL registration errors on the client's PC when they try to install the app. I used the VS.NET template to create the msi. What gives??? :confused: I should add that the target system had the SOAP SDK and the .NET framework installed on it prior to the app being installed. Any ideas why the install is getting errors? I thought .NET was not suppose to register DLL's.
What registration errors for what .DLL's? Compared to the Package and Deployment Wizard in VB6, the new Deployment Projects are easier and FAR more flexible. Since your using 3rd party DLL's, you still have to make sure that those DLL's get into the .MSI and are registered properly, if needed. The new Deployment Projects DO make deployment easier, but it can't follow the dependancy trail of every single DLL, that MIGHT be called by your app. RageInTheMachine9532
-
What registration errors for what .DLL's? Compared to the Package and Deployment Wizard in VB6, the new Deployment Projects are easier and FAR more flexible. Since your using 3rd party DLL's, you still have to make sure that those DLL's get into the .MSI and are registered properly, if needed. The new Deployment Projects DO make deployment easier, but it can't follow the dependancy trail of every single DLL, that MIGHT be called by your app. RageInTheMachine9532
They are getting errors on MSSOAP30.DLL and MSXML4.DLL. The errors say "COM Object with CLSID = "...."... unable to register. When the client tries to register the DLL's manually (those that were copied during the install into the app's subdirectory) the REGSVR32 reports a "no entry point" error. I am assuming that the DLL's do "get into the .MSI" because they are copied to the target machine during the install. What am I missing?