distributing Windows app

[Scott]

Hi Everyone,

I created a basic winforms app whose only purpose in life is to launch an
HTML page on an installation CD. The winform app is launch.exe and is
specified in the autorun.inf so it autoplays when the CD is inserted.
Everything was working fine... until my partner pointed out the launch.exe
generates an error on systems that do not have the .net framework installed.
So, back to the drawing board, I had to publish the app to get the .net
framework bootstrapped. Before this I simply built the solution but that
didn't include the prerequisites in the build process.
Now, I have this published app and everything seems to be working fine
again. The issue is I have some files like .application, .exe.manifest,
..config.deploy, etc. that must be included on the CD or the install will fail.
Is there any way I can cleanup these files? Is there a better way to deploy
my app?

Thanks,
Scott

[Scott]

an update...

The published launch.exe will not autorun. The launch.exe that I built and
manually copied to my CD autoruns just fine. The problem with the latter
approach is I need to check for the .net 2.0 framework and install it if it's
not present. Can I just build this simple .exe and later attach it to a
bootstrapping mechanism?

Any suggestions for resolving this issue?

Thanks,
Scott
"Scott" wrote:

Hi Everyone,

I created a basic winforms app whose only purpose in life is to launch an
HTML page on an installation CD. The winform app is launch.exe and is
specified in the autorun.inf so it autoplays when the CD is inserted.
Everything was working fine... until my partner pointed out the launch.exe
generates an error on systems that do not have the .net framework installed.
So, back to the drawing board, I had to publish the app to get the .net
framework bootstrapped. Before this I simply built the solution but that
didn't include the prerequisites in the build process.
Now, I have this published app and everything seems to be working fine
again. The issue is I have some files like .application, .exe.manifest,
.config.deploy, etc. that must be included on the CD or the install will fail.
Is there any way I can cleanup these files? Is there a better way to deploy
my app?

Thanks,
Scott

[Patrice]

Do you really have to launch an EXE file ? I would try to use the name of
the HTML page. Not sure in the context of autorun but IMO it should have the
usual behavior that is launching the associated application...

--
Patrice

"Scott" <Sc***@discussions.microsoft.com> a écrit dans le message de news:
3F**********************************@microsoft.com...

an update...

The published launch.exe will not autorun. The launch.exe that I built and
manually copied to my CD autoruns just fine. The problem with the latter
approach is I need to check for the .net 2.0 framework and install it if
it's
not present. Can I just build this simple .exe and later attach it to a
bootstrapping mechanism?

Any suggestions for resolving this issue?

Thanks,
Scott
"Scott" wrote:

Hi Everyone,

I created a basic winforms app whose only purpose in life is to launch an
HTML page on an installation CD. The winform app is launch.exe and is
specified in the autorun.inf so it autoplays when the CD is inserted.
Everything was working fine... until my partner pointed out the
launch.exe
generates an error on systems that do not have the .net framework
installed.
So, back to the drawing board, I had to publish the app to get the .net
framework bootstrapped. Before this I simply built the solution but that
didn't include the prerequisites in the build process.
Now, I have this published app and everything seems to be working fine
again. The issue is I have some files like .application, .exe.manifest,
.config.deploy, etc. that must be included on the CD or the install will
fail.
Is there any way I can cleanup these files? Is there a better way to
deploy
my app?

Thanks,
Scott

[Scott]

I tried specifying the .html file in the autorun.inf file. When the CD was
inserted, a msgbox was disaplyed saying "d:\ ... not a valid win32
application"
"Patrice" wrote:

Do you really have to launch an EXE file ? I would try to use the name of
the HTML page. Not sure in the context of autorun but IMO it should have the
usual behavior that is launching the associated application...

--
Patrice

"Scott" <Sc***@discussions.microsoft.com> a écrit dans le message de news:
3F**********************************@microsoft.com...

an update...

The published launch.exe will not autorun. The launch.exe that I built and
manually copied to my CD autoruns just fine. The problem with the latter
approach is I need to check for the .net 2.0 framework and install it if
it's
not present. Can I just build this simple .exe and later attach it to a
bootstrapping mechanism?

Any suggestions for resolving this issue?

Thanks,
Scott
"Scott" wrote:

Hi Everyone,

I created a basic winforms app whose only purpose in life is to launch an
HTML page on an installation CD. The winform app is launch.exe and is
specified in the autorun.inf so it autoplays when the CD is inserted.
Everything was working fine... until my partner pointed out the
launch.exe
generates an error on systems that do not have the .net framework
installed.
So, back to the drawing board, I had to publish the app to get the .net
framework bootstrapped. Before this I simply built the solution but that
didn't include the prerequisites in the build process.
Now, I have this published app and everything seems to be working fine
again. The issue is I have some files like .application, .exe.manifest,
.config.deploy, etc. that must be included on the CD or the install will
fail.
Is there any way I can cleanup these files? Is there a better way to
deploy
my app?

Thanks,
Scott