N
nautonnier
Hello,
I've posted this question on a couple of other newsgroups but no one
has responded but I really need to know if this can be done and I
can't imagine I'm the only one who wants to do it.
I'm working on an application that is installed via ClickOnce. It has
the standard .NET 2.0 prerequisite as well as the Crystal Reports
Viewer. Both of these packages are included in VS.NET 2005. Developers
have three choices in how to include any prerequisites in the
bootstrapper: 1) Use the manufacturer's URL embeded in the
package.xml; 2) Use the location that the app was published to; and 3)
Use a predetermined, static URL.
The problem is I work for an ISV which means we create products for
sale to others. Option 3 doesn't work for an obvious reason as this
product will go to others so a static URL makes no sense. Option 2 is
sort of the same as I publish to an internal server for use and
testing but that URL is, again, meaningless to an end client. Option 1
would probably work most of the time but I want to avoid any
situations where the network is restrictive where outside URLs are
concerned (i.e. I would rather the client host all the prerequisites
on their own servers and own all the responsibility).
The ideal solution would be to grab the URL from a config file but I
would also completely accept being able to have a relative path and
the folder structure would just have to remain static across
customers.
Does anybody have an idea as to how to do this? VS.NET won't accept
anything but to what amounts to a FQDN.
Any ideas would be greatly appreciated,
nautonnier
I've posted this question on a couple of other newsgroups but no one
has responded but I really need to know if this can be done and I
can't imagine I'm the only one who wants to do it.
I'm working on an application that is installed via ClickOnce. It has
the standard .NET 2.0 prerequisite as well as the Crystal Reports
Viewer. Both of these packages are included in VS.NET 2005. Developers
have three choices in how to include any prerequisites in the
bootstrapper: 1) Use the manufacturer's URL embeded in the
package.xml; 2) Use the location that the app was published to; and 3)
Use a predetermined, static URL.
The problem is I work for an ISV which means we create products for
sale to others. Option 3 doesn't work for an obvious reason as this
product will go to others so a static URL makes no sense. Option 2 is
sort of the same as I publish to an internal server for use and
testing but that URL is, again, meaningless to an end client. Option 1
would probably work most of the time but I want to avoid any
situations where the network is restrictive where outside URLs are
concerned (i.e. I would rather the client host all the prerequisites
on their own servers and own all the responsibility).
The ideal solution would be to grab the URL from a config file but I
would also completely accept being able to have a relative path and
the folder structure would just have to remain static across
customers.
Does anybody have an idea as to how to do this? VS.NET won't accept
anything but to what amounts to a FQDN.
Any ideas would be greatly appreciated,
nautonnier