| Dart Home | PowerTCP WebServer for ActiveX | Custom Development | Reply | PowerTCP WebServer for ActiveX Topics | Forums |
| Author | Forum: PowerTCP WebServer for ActiveX Topic: Deployment Problem |
| raymclain From: Oklahoma City, OK USA Posts: 4 Member Since: 01/17/12 |
posted January 17, 2012 9:36 PM Hello, I have designed a Visual Basic.Net application that makes use of the Dart Web Server for ActiveX control. When I run the program on my Dev machine, it works fine; however, when I attempt to deploy it to a different machine, I get a "debug assertion error" in line 172 of Atlcomcli.h every time I attempt to open a web page. I opened Atlcomcli.h in a debugger and found the following code at line 172: T& operator*() const { ATLASSERT(P != NULL); return *P; } The web server starts, pauses, and stops without error; the problem only occurs when an HTTP request is made from the server. Is there something I may have missed when I deployed my Visual Studio setup project? All of the DLL's that were referenced in the Visual Basic development project when I added the Dart Web Server ActiveX control to the form have also been included as dependencies in the setup project and assigned to be copied to the application folder. Any help would be greatly appreciated! Thanks! Mike |
| raymclain From: Oklahoma City, OK USA Posts: 4 Member Since: 01/17/12 |
posted January 18, 2012 11:05 AM Also, the name of the class in Atlcomcli.h that contains that section of code from line 172 is CComPtrBase. Because the T& member of the class is a constant, I assume there is a function somewhere that is attempting to change it or assign a null value to it? |
| Nick B (Admin) From: Utica, NY USA Posts: 619 Member Since: 05/25/10 Extra Support Options Custom Application Development |
posted January 18, 2012 3:16 PM Hello, What dlls are you deploying? Did you deploy and com-register the Dart dlls from System32 (or SysWOW64)? You can see a list of the dlls and dependencies you must deploy in the Distribution help topic in the help documentation. If that does not resolve your issue, can you explain what you're doing that causes this error? ------ |
| raymclain From: Oklahoma City, OK USA Posts: 4 Member Since: 01/17/12 |
posted January 23, 2012 1:24 PM Before I release a new VB.Net deployment, is it correct that: 1) The main DLL should go in the application folder of the target machine And 2) The dependency DLL's should go in the Windows\System32 folder of the target machine 3) If not automatically licensed by the application, the development license on the development machine gets installed to the registry on the target machine Are these the correct steps for deployment? |
| Nick B (Admin) From: Utica, NY USA Posts: 619 Member Since: 05/25/10 Extra Support Options Custom Application Development |
posted January 23, 2012 2:39 PM Hello, What do you mean by 'main' dll? There should be two interop dlls in your bin/(release or debug) folder; they should be deployed along with your exe, yes. The actual dlls are not copied there by the compiler. The component dll and its dependencies should be deployed to system32, or SysWOW64 if on a 64-bit machine, and COM registered. For compiled applications, the license is compiled into the executable. For scripted environments, see the 'Distribution in scripted environments' section in the Distribution topic in the help documentation. ------ |
| raymclain From: Oklahoma City, OK USA Posts: 4 Member Since: 01/17/12 |
posted January 30, 2012 3:43 AM By "main DLL", I was referring to the Ax.Interop DLL that goes in the application folder. VB.Net automatically drops the other Interop DLL in. Assigning the dependencies to the System32 folder did the trick. My app is now deplorable on any computer. Thanks for your assistance! |
| Reply | PowerTCP WebServer for ActiveX Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|