I havent looked into this to deep but I dont know how to do this…..
In C# you see constructions like this…
foreach (string mystr in bla bla)
In VB.NET this would be
Dim Mystr as String
For Each Mystr in BlaBla
Is it possible in VB.Net to use a same kind of construct , now I have to declare it before the foreach…
I was reading the posts of my favorite bloggers and came across an exellent article about pipelines.
This post handles some interesting points.
- Complete explanation on how to…
- Execute XPATH queries on STREAMING XML
have fun with it.
Have a look at this article and see how awesome the improvements in YUKON DTS are
I had a read of this article about SOA . If people think SOA is great they really should have a look at BizTalk.
After the read of the article I wonder if Biztalk = SOA and SOA = Biztalk ????
Well we are all talking about coding standars and stuff like that. I found a VERY intresting part on the internet about quantifying users. I think this is equally important as coding standards.
read the article here
I guess we all know a “Post Turtle Manager“
All, Just to let you know below some more information on building scalable .NET applications
a performance killer is the CLR build mode being used.. almost every .net app runs in the “workstation build” mode instead of server build. (even microsoft apps like reporting server)
The difference is that besides the Garbage Collection impact, the workstation mode dll will only use 1.5 – 2 cpu’s versus all available 8,16 or 32 cpu’s
basically blocking serious throughput. (we have seen apps that after we forced it to run in server mode, the throughput went up by a factor 3x..)
Easy check to see in what mode it runs, is to check which dll the app is using :
when it runs in the workstation CLR mode , it is recognisable by the usage of MSCORWKS.DLL , the server clr uses MSCORSVR.DLL.
( A utility like www.Sysinternals.com – Process Explorer will show it quickly and also which threads a truly doing some work within the app)
click here to see how to enable Server Build mode
Click here to see how this setting affects the number of processors
From: Scott Woodgate
Sent: Saturday, August 14, 2004 12:01 AM
To: BizTalk News Updates – Public
Subject: IMPORTANT: BizTalk Server 2004 fixes for Windows XP SP2 and .NET FW 1.1 SP1
Please share this information broadly with your customers and partners
1) BizTalk Server 2004 will stop functioning after the installation of Windows XP SP2 due to changes in the DCOM security model. Windows XP SP2 is available for download now and will be pushed through WindowsUpdate in late August.
Modify the registry with the instructions below to resolve this issue:
2) The BizTalk Server 2004 Rules Engine component will stop functioning after the installation of the .NET FW 1.1 SP1 due to issues in our implementation which are now resolved. It is expected that all other existing user-level code written in the .NET FW 1.1 will continue to work in the .NET FW 1.1 SP1. The .NET Framework 1.1 SP1 is not yet publically available but will become available shortly.
Download the hotfix for the rules engine component to resolve this issue:
N.B. This hotfix is supported both on the .NET FW 1.1 and the .NET FW 1.1 SP1 so you can install it today if you like.