BCM and .NET 2.0

[Brian Leach]

We develop an application that requires .NET 2.0. When .NET 2.0 is
installed, BCM won't load, and worse, it prevents Outlook from loading.

I've seen a number of posts complaining about this, but no clear solutions.
Has Microsoft ever addressed this issue?

 

[Luther]

We develop an application that requires .NET 2.0. When .NET 2.0 is
installed, BCM won't load, and worse, it prevents Outlook from loading.

I've seen a number of posts complaining about this, but no clear solutions.
Has Microsoft ever addressed this issue?

What version of BCM? Is .NET 1.1 also installed?

 

[Brian Leach]

I don't know exactly what version of BCM, but we've had several customers
report that this happened to them, and in all cases ir was a version of BCM
that came preinstalled on their laptop. In cases where we asked how old,
the laptops were at least two years old. In both cases .NET 1.1 was already
installed -- doesn't BCM require that to run anyway?

 

[Luther]

I don't know exactly what version of BCM, but we've had several customers
report that this happened to them, and in all cases ir was a version of BCM
that came preinstalled on their laptop. In cases where we asked how old,
the laptops were at least two years old. In both cases .NET 1.1 was already
installed -- doesn't BCM require that to run anyway?







- Show quoted text -

The first step would be to ensure that these machines have all the
latest Service Packs and patches for Office, BCM and .NET.

 

[Brian Leach]

To recap, the problem is that we are deploying a product that use .NET 2.0,
and it seems that installing .NET 2.0 breaks BCM.

Are you suggesting that in our installer, we determine if BCM is installed,
and if it is, make sure that the user is running the latest Service Packs
and patches for Office and BCM? This seems like a lot to go through to
deploy a simple .NET 2.0 application.

I was hoping for a simple workaround to make it not break BCM . . .

/brian

 

[Luther]

To recap, the problem is that we are deploying a product that use .NET 2.0,
and it seems that installing .NET 2.0 breaks BCM.

Are you suggesting that in our installer, we determine if BCM is installed,
and if it is, make sure that the user is running the latest Service Packs
and patches for Office and BCM? This seems like a lot to go through to
deploy a simple .NET 2.0 application.

I was hoping for a simple workaround to make it not break BCM . . .

/brian







- Show quoted text -

I recall that when .NET 2 was released, some BCM installations ran
into problems, but those reports of those problems went down after a
while, so I suspect that some patch fixed the problem in .NET 1.1. You
could also try uninstalling 1.1 and reinstalling it.

If you want to identify what the actual problem is, running a Fusion
of BCM startup has helped in the past. The fusion log viewer utility
is bundled with the .NET SDKs.

If your machines have BCM v1 installed, you should definately update
them to v2 (AKA BCM 2003 Update).

Having the latest patches and SPs recommended by Microsoft Update is a
good practice in general.