HTTP Version compatibility

[Calvin KD]

Does anyone know if there's any issues involving versions of .Net Framework,
Visual Studio and HTTP which might cause a compatibility problem?
We currently using VS1.1 for our web apps (C#) and the app seems to be up
and and down quite regularly on production and we're not quite sure why. Our
techies told us that because we're (developers) using the wrong version of
http, 1 instead of 1.1, which cause some sort of compatibility issues and/or
memory leaks...blah blah blah.
Without going into too much details and politics, I just like to know if
there's any connections between Visual Studio versions, .Net Framework and
the http versions which might cause compatibility issues.

Any suggestion is greatly appreciated.
Calvin

[Christopher Reed]

Not that I'm an expert, but if I remember correctly, the HTTP protocol is
determined by the web server (IIS). You can set the HTML version in your
ASP.NET application, but that's not directly relevant to the protocol.

In other words, your techies are responsible for the protocol settings
(actually they're really not) and if they didn't know that, then they need
more training.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Calvin KD" <Ca******@discussions.microsoft.com> wrote in message
news:28**********************************@microsof t.com...

Does anyone know if there's any issues involving versions of .Net
Framework,
Visual Studio and HTTP which might cause a compatibility problem?
We currently using VS1.1 for our web apps (C#) and the app seems to be up
and and down quite regularly on production and we're not quite sure why.
Our
techies told us that because we're (developers) using the wrong version of
http, 1 instead of 1.1, which cause some sort of compatibility issues
and/or
memory leaks...blah blah blah.
Without going into too much details and politics, I just like to know if
there's any connections between Visual Studio versions, .Net Framework and
the http versions which might cause compatibility issues.

Any suggestion is greatly appreciated.
Calvin

[Calvin KD]

Thanks Christopher,
That's exactly how I understand it but since I'm no expert either, that's
why I was seeking further advice from the wider community.
Thanks heaps,
Cheers,
Calvin

"Christopher Reed" wrote:

Not that I'm an expert, but if I remember correctly, the HTTP protocol is
determined by the web server (IIS). You can set the HTML version in your
ASP.NET application, but that's not directly relevant to the protocol.

In other words, your techies are responsible for the protocol settings
(actually they're really not) and if they didn't know that, then they need
more training.
--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

"Calvin KD" <Ca******@discussions.microsoft.com> wrote in message
news:28**********************************@microsof t.com...

Does anyone know if there's any issues involving versions of .Net
Framework,
Visual Studio and HTTP which might cause a compatibility problem?
We currently using VS1.1 for our web apps (C#) and the app seems to be up
and and down quite regularly on production and we're not quite sure why.
Our
techies told us that because we're (developers) using the wrong version of
http, 1 instead of 1.1, which cause some sort of compatibility issues
and/or
memory leaks...blah blah blah.
Without going into too much details and politics, I just like to know if
there's any connections between Visual Studio versions, .Net Framework and
the http versions which might cause compatibility issues.

Any suggestion is greatly appreciated.
Calvin