In the application's IIS configuration, you need to specify the correct
version of .NET. By default, the highest version number is used.
Mike Ober.
> When I put a .NET assembly (.exe) generated with VS.NET 2003 on a Webserver
> (IIS) and try to invoke it over a Browser (IE) from another station the
[quoted text clipped - 9 lines]
>
> Any ideas why?
Christian Schönig - 03 Jul 2006 14:21 GMT
Hi Mike,
that sounds correct, but how can I put this in a normal application?
I put the following in the App.config file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>;
</startup>
</configuration>
but it did not help!
Thanks for Your advice!
> In the application's IIS configuration, you need to specify the correct
> version of .NET. By default, the highest version number is used.
[quoted text clipped - 15 lines]
> >
> > Any ideas why?
Michael D. Ober - 03 Jul 2006 15:24 GMT
The setting is in the IIS Administration utility itself. You need administrator access to the IIS Server. Unfortunately, it's not in your web application.
Mike.
Hi Mike,
that sounds correct, but how can I put this in a normal application?
I put the following in the App.config file:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>;
</startup>
</configuration>
but it did not help!
Thanks for Your advice!
"Michael D. Ober" <obermd.@.alum.mit.edu.nospam> schrieb im Newsbeitrag news:Sj7qg.2265$PE1.1728@newsread2.news.pas.earthlink.net...
> In the application's IIS configuration, you need to specify the correct
> version of .NET. By default, the highest version number is used.
>
> Mike Ober.
>
> "Christian Schönig" <cschoenig@weber-online.com> wrote in message
> news:%2372%23LSpnGHA.3528@TK2MSFTNGP04.phx.gbl...
> > When I put a .NET assembly (.exe) generated with VS.NET 2003 on a
> Webserver
> > (IIS) and try to invoke it over a Browser (IE) from another station the
> > following happens:
> >
> > 1. under .NET 1.1 the application gets executed (normal appearance)
> > 2. as soon .NET 2.0 is installed as well, the application is not executed.
> > It comes up the dialog to execute or save the Application in a folder. It
> > looks like a coumputer with no .NET framework at all >
> > The Application in our case has to be started right away. We can not store
> > it locally and execute it from there! We need the not touch deployment
> > there!
> >
> > Any ideas why?
> >
> >
> >
Christian Schönig - 04 Jul 2006 10:03 GMT
Hi,
i found a interesting thread in
http://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=93820
where is stated, that no touch deployment is discontinoued in V2.0! There
are workarounds which seem to help for certain applications!
So my problem is clear now and there is kind of solution for it!
Thanks for all replies!
Chris.
> In the application's IIS configuration, you need to specify the correct
> version of .NET. By default, the highest version number is used.
[quoted text clipped - 15 lines]
> >
> > Any ideas why?