|
Home > Archive > BizTalk Server Applications Integration > May 2006 > BizTalk 2004 and .NET 2.0
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BizTalk 2004 and .NET 2.0
|
|
| anetasalomonsen@hotmail.com 2006-03-17, 7:49 am |
| We have a system containing BizTalk-applications, web-applications and
and common-layer used by both the BizTalk and all the web-klients. For
BizTalk to be able to use the common-layer, all the common-assemblyes
are put into GAC.
Now we are about to switch from Visual Studio 2003 to Visual Studio
2005. We do not want to switch to BizTalk 2006 just yet. Therfore we
can not convert the BizTalk-projects to VS2005. The web-app-projects
will be converted to VS2005. But what about the common-projects?
Is the only way to duplicate the common-projects (one set for VS2005
and one for VS2003) until we convert the BizTalk-projects as well?
Or is it possible for us to only have VS2005-common-projects. Is it
possible to put 2.0-assemblies in the .net 1.1-GAC? And will BizTalk be
able to consume these assemblies?
Any thoughts, tips and advises are highly appreciated!
| |
| Adrian Hamza [MSFT] 2006-03-17, 5:52 pm |
| A process can load only one version of the .Net Framework. This means that
a BizTalk Host Instance process will load one of the .Net Framework
versions.
.Net Framework 2.0 can execute 1.1 assemblies. If it's the other way
around, then you have a problem.
I don't know if you can force BizTalk to load a particular .Net Framework
nor if BT04 supports .Net Framework 2.0.
I would look at policy/config files to see if it can be configured.
One solution would be to have the common assemblies built in 1.1 so that
they can run no matter what .Net Framework you use.
This posting is provided "AS IS" with no warranties, and confers no rights.
Adrian Hamza [MSFT]
http://blogs.msdn.com/ahamza/
My blog on BizTalk 2006
Windows SharePoint Services adapter
--------------------[vbcol=seagreen]
09:49:10 GMT)[vbcol=seagreen]
.NET CLR 1.1.4322; .NET CLR 2.0. 50727),gzip(gfe),gzip(gfe)[vbcol=seagree
n]
TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.gigan
ews.com!postnews.google.com!z34g2000cwc.googlegroups.com!not-for-mail[vbcol=seagreen]
| |
|
| Take a look at the thread titled 'BTS 2004 and .Net 2.0 not getting along?
This states that BTS 2004 will NOT run on Framework 2.0 then explains how to
load .Net 1.1. I had a similar problem after installing SQL Server
Management Studio, which uses Framework 2.0.
"Adrian Hamza [MSFT]" wrote:
> A process can load only one version of the .Net Framework. This means that
> a BizTalk Host Instance process will load one of the .Net Framework
> versions.
> .Net Framework 2.0 can execute 1.1 assemblies. If it's the other way
> around, then you have a problem.
>
> I don't know if you can force BizTalk to load a particular .Net Framework
> nor if BT04 supports .Net Framework 2.0.
> I would look at policy/config files to see if it can be configured.
>
> One solution would be to have the common assemblies built in 1.1 so that
> they can run no matter what .Net Framework you use.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Adrian Hamza [MSFT]
> http://blogs.msdn.com/ahamza/
> My blog on BizTalk 2006
> Windows SharePoint Services adapter
>
> --------------------
> 09:49:10 GMT)
> .NET CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
> TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
> ne.de!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.gigan
> ews.com!postnews.google.com!z34g2000cwc.googlegroups.com!not-for-mail
>
>
|
|
|
|
|