Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > BIZTALKSERVER (TECHNET) > Biztalk Server 2002 and Visual Studio.NET 2003
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 26th August 21:36
benjamin fallar iii
External User
 
Posts: 1
Default Biztalk Server 2002 and Visual Studio.NET 2003



Hi,

I'm still using BizTalk 2002 and Visual Studio.NET 2002. Recently, we
upgraded to Visual Studio.NET 2003. I would like to know how to upgrade
our development for BizTalk to support Visual Studio.NET 2003,
especially the Microsoft.NET Toolkit for BizTalk.

Please help ASAP!
  Reply With Quote


  sponsored links


2 27th August 13:15
steve
External User
 
Posts: 1
Default Biztalk Server 2002 and Visual Studio.NET 2003



Simple. The Microsoft.NET toolkit for BizTalk works with VS.NET 2003.
And more then likely, you can open your current VS 2002 projects with
VS 2003 and it will auto convert them with no problems.
  Reply With Quote
3 26th September 16:33
ryan harper
External User
 
Posts: 1
Default Biztalk Server 2002 and Visual Studio.NET 2003


Acutally it only works with framework 1.0. Does anyone have it working with
1.1 or 2.0? I changed the setup.cmd to point to my 1.1 install and the setup
ran fine but biztalk orchestartions would not start unless I installed 1.0
and removed 1.1.
  Reply With Quote
4 26th September 16:34
jeff lynch
External User
 
Posts: 1
Default Biztalk Server 2002 and Visual Studio.NET 2003


I've had it working with the .NET 1.1 Framework but it won't work with 2.0.

--
Jeff Lynch
"Ramblings From A [Microsoft] Connected Universe"
http://codebetter.com/blogs/jeff.lynch
  Reply With Quote
5 27th September 03:28
ryan harper
External User
 
Posts: 1
Default Biztalk Server 2002 and Visual Studio.NET 2003


How did you get it to work? Did you just change the setup.cmd script?
  Reply With Quote
6 27th September 03:29
jeff lynch
External User
 
Posts: 1
Default Biztalk Server 2002 and Visual Studio.NET 2003


I'm going from memory here but I believe all I did was change the .cmd to
point to the C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 folder. Then I
recompiled the xlang schedules. Any custom .NET components also need to
point to the new Framework and be recompiled.

--
Jeff Lynch
"Ramblings From A [Microsoft] Connected Universe"
http://codebetter.com/blogs/jeff.lynch
  Reply With Quote
7 29th September 16:12
ryan harper
External User
 
Posts: 1
Default Biztalk Server 2002 and Visual Studio.NET 2003


Hmm...I did this and my preprocessors execute okay but when my xlang schedule
starts, non of the AIC's get executed and it just stops (watching it in xlang
monitor). If I execute the process with framework 1.0 the AIC's get executed
and all is okay. I have burned more that two days trying to get this to
work. Any ideas?
  Reply With Quote


  sponsored links


Reply


Thread Tools
Display Modes




Copyright © 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666