Launch Condition error icon problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ron - 14 Jun 2005 17:32 GMT

I have VS.NET 2003 Prof + .NET BootStrapper PlugIn running on Win2000 Prof.
Net Framework v1.1. Everything was working well until I re-installed Windows
and VS.NET. Now all the Setup Launch Condition entries have an error icon
(the white exclamation mark in a red circle). The setup app will build ok
and install the .NET Framework and my app, with no errors found, but I
cannot cure the error status of the Launch Conditions. Has anyone else had
this problem and found the solution. I have tried repairing VS.NET but with
no effect. I have tried looking on Google, but all the posts seem to be
about just adding Launch Conditions.
Many Thanks,
Ron.

Reply to this Message

Phil Wilson - 16 Jun 2005 02:34 GMT

My .NET Framework launch conditions have always looked like that - I thought
it was normal !

Signature

Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

>I have VS.NET 2003 Prof + .NET BootStrapper PlugIn running on Win2000 Prof.
> Net Framework v1.1. Everything was working well until I re-installed
[quoted text clipped - 9 lines]
> Many Thanks,
> Ron.

Reply to this Message

Ron - 16 Jun 2005 14:06 GMT

> My .NET Framework launch conditions have always looked like that - I thought
> it was normal !

Hi Phil. Thanks for the response. The odd thing is the .NET Framework launch
condition is not automatically set up - I have to add it via the Action
menu. I never had any problem before (I have used Visual Studio .NET 2003
for about a year) but now this apparent error occurs. As the setup works
just fine, I wonder if it is just a visual icon error, and not a real error?

Regards,
Ron.

Reply to this Message

Phil Wilson - 22 Jun 2005 00:28 GMT

I think VS is pretty smart about adding that launch condition when needed.
You're really installing managed code? I think maybe that if you build a
merge module project containing managed code it doesn't add a launch
condition, but that's probably deliberate, and I can't recall if it the
launch condition gets added when the merge module is incorporated into a MSI
project. Just wondering if that's what you're doing.

Signature

Phil Wilson [MVP Windows Installer]
----

>
>> My .NET Framework launch conditions have always looked like that - I
[quoted text clipped - 10 lines]
> Regards,
> Ron.

Reply to this Message

Ron - 22 Jun 2005 17:34 GMT

> I think VS is pretty smart about adding that launch condition when needed.
> You're really installing managed code? I think maybe that if you build a
> merge module project containing managed code it doesn't add a launch
> condition, but that's probably deliberate, and I can't recall if it the
> launch condition gets added when the merge module is incorporated into a MSI
> project. Just wondering if that's what you're doing.

<snip>

I wonder if it has anything to do with me adding Crystal Reports to my app.
When I did the compiler complained that my project was no longer CLS
compliant, so I had to remove the [assembly:CLSCompliant(true)] attribute
from my project .cs files. Perhaps I will run FXCop on the project. It may
show me something. I don't believe the problem is with the NET Framework
setup because I get the error icon with any condition I add. Anyway, as I
said, everything builds, installs and runs fine, so I am not really worried
about it.
Well, I have wasted enough of your time, Phil, so thanks very much for the
advice.
Ron.

Reply to this Message

Launch Condition error icon problem

Free Magazines