moabiker31
Programmer
VB 2005
I'm deploying an app to another developer that has the same 3rd party tools installed on his pc as I do. When he installs this app it "breaks" his development environment by changing the registration path of all the ocx's to the app's folder I gave him rather than the path where the ocx was installed originally. So when he runs an app from the IDE, it can't find the controls since the IDE is expecting the ocx to be registered at C:\blah but it's actually registered at D:\blah. Within the deployment project, each of the ocx's have Exclude set to True; and Register is set to vsdrfDoNotRegister. Any idea why those ocx's are getting registered or is there a different cause for the IDE to not work? Thanks.
I'm deploying an app to another developer that has the same 3rd party tools installed on his pc as I do. When he installs this app it "breaks" his development environment by changing the registration path of all the ocx's to the app's folder I gave him rather than the path where the ocx was installed originally. So when he runs an app from the IDE, it can't find the controls since the IDE is expecting the ocx to be registered at C:\blah but it's actually registered at D:\blah. Within the deployment project, each of the ocx's have Exclude set to True; and Register is set to vsdrfDoNotRegister. Any idea why those ocx's are getting registered or is there a different cause for the IDE to not work? Thanks.
