AtillaTheMagyar
Programmer
I have written my first C# app and am in the process of distributing it (yeah!). It will be bundled with some other apps - however there are no issues with those.
Microsoft has been kind enough to create a bootstrapper for dotnetfx.exe which will launch my MSI file after the .net framework is installed. This bootstrapper seems to work fine, until I launch it from a DemoShield project (the DemoShield project launches when the CD is inserted - autorun, ya know).
Anyway, when I run the setup.exe by itself, everything works just fine. It's just when the setup.exe is launched from DemoShield that the problem happens.
This might be not be a .Net issue, it might be an issue with DemoShield. However, I thought I would throw it out and see if anyone has seen anything like this before.
Any insights would be very welcome.
Microsoft has been kind enough to create a bootstrapper for dotnetfx.exe which will launch my MSI file after the .net framework is installed. This bootstrapper seems to work fine, until I launch it from a DemoShield project (the DemoShield project launches when the CD is inserted - autorun, ya know).
Anyway, when I run the setup.exe by itself, everything works just fine. It's just when the setup.exe is launched from DemoShield that the problem happens.
This might be not be a .Net issue, it might be an issue with DemoShield. However, I thought I would throw it out and see if anyone has seen anything like this before.
Any insights would be very welcome.