When you design a BizTalk orchestration and you want to suspend the orchestration with a ThrowException shape, it is useful to initialize the exception variable in an Expression shape with a descriptive error message in advance.
Example:
incomingMessageNotFoundException = new System.Exception("No referenced incomingMessage found"); (*)
(*): In this example incomingMessageNotFoundException is the exception variable of type System.Exception.
The result is that the error message "No referenced incomingMessage found" is shown in the Error Information tab of the Service Details window if an orchestration instance gets suspended because of this error. If you do not initialize the variable yourself, BizTalk uses the default constructor and you only get the information that an exception of type System.Exception has occured in your orchestration. This does not help much.
Dienstag, 10. März 2009
Samstag, 11. Oktober 2008
Microsoft Certificate
Yesterday, I earned my first Microsoft Certifacte. I purchased Exam 70-235 as part of the Microsoft Certified Program.
_511.png)
_511.png)
Freitag, 12. September 2008
How to accelerate VPCs in MS Virtual PC 2007
Since yesterday, I was quite sure that my host OS Windows Vista has a negative effect on the performance of my VPCs. I am talking about lazy mouse movement choppy scrolling and stuff like that.
After reading this post, I thought that VMWare could solve this problem. So, I downloaded VMWare Converter and a 30-days-evaluation version of VMWare Workstation 6. During setup of VMWare Tools on the guest OS a text message popped up saying, that I can get better graphic performance if I'd change something in the display properties. I was not aware of the described switch. Afterwards, there was a noticeable acceleration.
Because it was a windows internal property, I went back to my VPC and changed it there as well. The difference in Virtual PC was much more drastic. It solved all the performance problems I had. Now, I can work with the guest OS in a familiar speed. Finally, I was wrong and Virtual PC has no problems with Windows Vista as host OS. The pic below shows the the settings, which have to be made.
(Location: Display properties, tab Settings, menu Advanced)
After reading this post, I thought that VMWare could solve this problem. So, I downloaded VMWare Converter and a 30-days-evaluation version of VMWare Workstation 6. During setup of VMWare Tools on the guest OS a text message popped up saying, that I can get better graphic performance if I'd change something in the display properties. I was not aware of the described switch. Afterwards, there was a noticeable acceleration.
Because it was a windows internal property, I went back to my VPC and changed it there as well. The difference in Virtual PC was much more drastic. It solved all the performance problems I had. Now, I can work with the guest OS in a familiar speed. Finally, I was wrong and Virtual PC has no problems with Windows Vista as host OS. The pic below shows the the settings, which have to be made.
(Location: Display properties, tab Settings, menu Advanced)
Abonnieren
Posts (Atom)