By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,594 Members | 3,291 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,594 IT Pros & Developers. It's quick & easy.

creating a .net setup project in vs 2003

P: n/a
pbj
my application was created in vb.net, vs 2003. the setup project was also
created in vs 2003. one of my application reviewers reported this:

The .Net link that is included in the setup is not the correct link, it's
outdated. The link should be changed from this
http://msdn.microsoft.com/library/de...vframework.asp to the new link, which
is this:
http://msdn.microsoft.com/netframewo...s/default.aspx.

since i put neither of these links into my setup. i assume it is something
generated automatically by the visual studio 2003 setup project. i am
guessing it comes into play when someone does not have .net installed.

anyone know how i might update this link in my setup project?

thanks.

Jul 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Yes, as the .NET setup project itself is dependent on presence of the .NET
framework on the target machine to run. There's a built-in launch check for
that in the setup project. That's where this link comes in to play.
Doesn't really seem to be really a crucial flaw. It seems to realize the
link is old
and provides a link to the relocated page (by the way that relocated URL
seems
different yet again to what your reviewer is suggesting - seems like
one can download the framework at either one though - "all roads lead to
Rome..."

You can probably see the .NET framework under Dependencies in your
setup project as "dotnetfxredist_x86.msm" (with the Exclude property set to
True).

Bottom line to me it's that you get there by following the link... (would be
nice
to change it though - but I doubt it can be done).

"pbj" wrote:
my application was created in vb.net, vs 2003. the setup project was also
created in vs 2003. one of my application reviewers reported this:

The .Net link that is included in the setup is not the correct link, it's
outdated. The link should be changed from this:
http://msdn.microsoft.com/library/de...vframework.asp to the new link, which
is this:
http://msdn.microsoft.com/netframewo...s/default.aspx.

since i put neither of these links into my setup. i assume it is something
generated automatically by the visual studio 2003 setup project. i am
guessing it comes into play when someone does not have .net installed.

anyone know how i might update this link in my setup project?

thanks.

Jul 21 '05 #2

P: n/a
pbj
i agree it seems trival since the link does forward correctly. i am
submitting my .net application setup to tucows.com as shareware. there
response was:

"Thank you for submitting your software for distribution on www.tucows.com.
Unfortunately, we are unable to accept your program at this time because the
..Net link that is included in the setup is not the correct link, it's
outdated. The link should be changed ..."

hence my quest.

"Ben Solomon" wrote:
Yes, as the .NET setup project itself is dependent on presence of the .NET
framework on the target machine to run. There's a built-in launch check for
that in the setup project. That's where this link comes in to play.
Doesn't really seem to be really a crucial flaw. It seems to realize the
link is old
and provides a link to the relocated page (by the way that relocated URL
seems
different yet again to what your reviewer is suggesting - seems like
one can download the framework at either one though - "all roads lead to
Rome..."

You can probably see the .NET framework under Dependencies in your
setup project as "dotnetfxredist_x86.msm" (with the Exclude property set to
True).

Bottom line to me it's that you get there by following the link... (would be
nice
to change it though - but I doubt it can be done).

"pbj" wrote:
my application was created in vb.net, vs 2003. the setup project was also
created in vs 2003. one of my application reviewers reported this:

The .Net link that is included in the setup is not the correct link, it's
outdated. The link should be changed from this:
http://msdn.microsoft.com/library/de...vframework.asp to the new link, which
is this:
http://msdn.microsoft.com/netframewo...s/default.aspx.

since i put neither of these links into my setup. i assume it is something
generated automatically by the visual studio 2003 setup project. i am
guessing it comes into play when someone does not have .net installed.

anyone know how i might update this link in my setup project?

thanks.

Jul 21 '05 #3

P: n/a
Understood - I've got Microsoft Development Environment 2003 version 7.1.3088
(SP 1)

I'd pursue a rebuild of the deployment aka setup making sure I've got the
latest and greatest dev. env. from MS...

"pbj" wrote:
i agree it seems trival since the link does forward correctly. i am
submitting my .net application setup to tucows.com as shareware. there
response was:

"Thank you for submitting your software for distribution on www.tucows.com.
Unfortunately, we are unable to accept your program at this time because the
.Net link that is included in the setup is not the correct link, it's
outdated. The link should be changed ..."

hence my quest.

"Ben Solomon" wrote:
Yes, as the .NET setup project itself is dependent on presence of the .NET
framework on the target machine to run. There's a built-in launch check for
that in the setup project. That's where this link comes in to play.
Doesn't really seem to be really a crucial flaw. It seems to realize the
link is old
and provides a link to the relocated page (by the way that relocated URL
seems
different yet again to what your reviewer is suggesting - seems like
one can download the framework at either one though - "all roads lead to
Rome..."

You can probably see the .NET framework under Dependencies in your
setup project as "dotnetfxredist_x86.msm" (with the Exclude property set to
True).

Bottom line to me it's that you get there by following the link... (would be
nice
to change it though - but I doubt it can be done).

"pbj" wrote:
my application was created in vb.net, vs 2003. the setup project was also
created in vs 2003. one of my application reviewers reported this:

The .Net link that is included in the setup is not the correct link, it's
outdated. The link should be changed from this:
http://msdn.microsoft.com/library/de...vframework.asp to the new link, which
is this:
http://msdn.microsoft.com/netframewo...s/default.aspx.

since i put neither of these links into my setup. i assume it is something
generated automatically by the visual studio 2003 setup project. i am
guessing it comes into play when someone does not have .net installed.

anyone know how i might update this link in my setup project?

thanks.

Jul 21 '05 #4

P: n/a
This link is part of the the Launch condition viewable in the setup project
Select the setup project in the solution explorer
from the toolbar select view->Editor->Launch Conditions
Select the ".NET Framework" launch condition
Press F4 to opne the property grid (if not already opened)
Change the InstallURL to your desired value
Rebuild

That should take care of your problem.

Todd Derksen
--------------------
Visual Basic Deployment Test Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: creating a .net setup project in vs 2003

Yes, as the .NET setup project itself is dependent on presence of the .NET
framework on the target machine to run. There's a built-in launch check forthat in the setup project. That's where this link comes in to play.
Doesn't really seem to be really a crucial flaw. It seems to realize the
link is old
and provides a link to the relocated page (by the way that relocated URL
seems
different yet again to what your reviewer is suggesting - seems like
one can download the framework at either one though - "all roads lead to
Rome..."

You can probably see the .NET framework under Dependencies in your
setup project as "dotnetfxredist_x86.msm" (with the Exclude property set toTrue).

Bottom line to me it's that you get there by following the link... (would benice
to change it though - but I doubt it can be done).

"pbj" wrote:
my application was created in vb.net, vs 2003. the setup project was also created in vs 2003. one of my application reviewers reported this:

The .Net link that is included in the setup is not the correct link, it's outdated. The link should be changed from this:
http://msdn.microsoft.com/library/de...ist/netdevfram
ework.asp to the new link, which is this:
http://msdn.microsoft.com/netframewo...s/default.aspx.

since i put neither of these links into my setup. i assume it is something generated automatically by the visual studio 2003 setup project. i am
guessing it comes into play when someone does not have .net installed.

anyone know how i might update this link in my setup project?

thanks.


Jul 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.