.NET 1.1 SP1 Problems?

[Mike Murphy]

Has anybody been experiencing problems with .NET 1.1 SP1? I installed it
from Windows Update, but the "Microsoft .NET Framework 1.1 Configuration"
dialog shows the build number prior to SP1! Further, examining .dll
versions in WINNT\Microsoft.NET\Framework\1.1.4322:

mscorcfg.dll: 1.1.4322.573
mscordbc.dll: 1.1.4322.2032

Further, I've been experiencing some spurious behavior in some of my .NET
applications that hasn't happened before. Just the above makes me paranoid,
can anybody tell me whether this is normal or not? It seems odd that the
configuration dialog can't tell whether the SP is installed or not. If there
is a "fixit" procedure, I would really be interested! Thanks!

Mike
mi**@jones-murphy.org

[Dicky Cheng]

I have the exactly same problem, I was installed it in my Win2000 server.
Anyone can help?

"Mike Murphy" <Mi********@discussions.microsoft.com> wrote in message
news:8E**********************************@microsof t.com...

I just noticed that knowledge base article #KB318785 has been updated 9/18 to indicate the funny dll versioning described below is expected. However, my Mscoree.dll is 1.1.4322.573, not .2032 as expected. Am I really the only
one experiencing this?

Mike

"Mike Murphy" wrote:

Has anybody been experiencing problems with .NET 1.1 SP1? I installed it from Windows Update, but the "Microsoft .NET Framework 1.1 Configuration" dialog shows the build number prior to SP1! Further, examining .dll
versions in WINNT\Microsoft.NET\Framework\1.1.4322:

mscorcfg.dll: 1.1.4322.573
mscordbc.dll: 1.1.4322.2032

Further, I've been experiencing some spurious behavior in some of my ..NET applications that hasn't happened before. Just the above makes me paranoid, can anybody tell me whether this is normal or not? It seems odd that the configuration dialog can't tell whether the SP is installed or not. If there is a "fixit" procedure, I would really be interested! Thanks!

Mike
mi**@jones-murphy.org

[Mike Murphy]

I just noticed that knowledge base article #KB318785 has been updated 9/18 to
indicate the funny dll versioning described below is expected. However, my
Mscoree.dll is 1.1.4322.573, not .2032 as expected. Am I really the only
one experiencing this?

Mike

"Mike Murphy" wrote:

Has anybody been experiencing problems with .NET 1.1 SP1? I installed it
from Windows Update, but the "Microsoft .NET Framework 1.1 Configuration"
dialog shows the build number prior to SP1! Further, examining .dll
versions in WINNT\Microsoft.NET\Framework\1.1.4322:

mscorcfg.dll: 1.1.4322.573
mscordbc.dll: 1.1.4322.2032

Further, I've been experiencing some spurious behavior in some of my .NET
applications that hasn't happened before. Just the above makes me paranoid,
can anybody tell me whether this is normal or not? It seems odd that the
configuration dialog can't tell whether the SP is installed or not. If there
is a "fixit" procedure, I would really be interested! Thanks!

Mike
mi**@jones-murphy.org

[Willy Denoyette [MVP]]

"Mike Murphy" <Mi********@discussions.microsoft.com> wrote in message
news:8E**********************************@microsof t.com...
However, my

Mscoree.dll is 1.1.4322.573, not .2032 as expected. Am I really the only

Mscoree.dll did not change so it kept it's build number. What problems do
you have with it?

Willy.

[Mike Murphy]

I have a database application where I am using alot of databinding
(textboxes, comboboxes), and it seems after reloading the datasets five or
six times, the databinding just stops working on SP1, but never fails pre-SP1.

I "reload" the datasets via the dataadapter .Fill() method. Should I
bracket the .Fill() with .SuspendBinding()/.ResumeBinding() to prevent this?
Recreating the datasets each time (via New()) prevents the problem on SP1,
but I don't like doing this.

Mike

"Willy Denoyette [MVP]" wrote:

"Mike Murphy" <Mi********@discussions.microsoft.com> wrote in message
news:8E**********************************@microsof t.com...
However, my

Mscoree.dll is 1.1.4322.573, not .2032 as expected. Am I really the only

Mscoree.dll did not change so it kept it's build number. What problems do
you have with it?

Willy.