BizTalk BAM Portal failure and configuration woes
- Open the command prompt and find your way to BM.exe (Program FilesBizTalk …tracking)
- Retrieve the current configuration information:
bm get-config -FileName:"BAM_Config.xml" - Update the config file to remove the reference to the current website:
<GlobalProperty Name="BAMVRoot">http://blah.blah.remove.this.URL</GlobalProperty> - Update the BAM configuration database:
bm update-config -FileName:"BAM_Config.xml" - Re-run the BizTalk Configuration Tool and re-configure the BAM Portal feature and you should be good to go
Conclusion…
Nothing in BizTalk is as it seems
BizTalk Error: Failed to grant permission to execute. (Exception from HRESULT: 0x80131418)
- Create a separate App Pool running as a user that has permission to the BizTalk Isolated Host (I just ran it as my BizTalk Iso service account as a shortcut)
- Make sure this app pool is running as classic mode and not integrated mode
- CHECK THE TRUST LEVEL to make sure it is appropriate … in my case I just set it to Full Trust to get it through my test
- Don’t for get to enable the receive location, it is not enabled by the wizard … you couldn’t imagine how many times I forgot to do this while trying to figure out why my darn service isn’t working again!
Well … hope this helps someone else!
Visual Studio Team Test: Web Tests and IE8
Silverlight 2.0: Creating an Offline Application (Smart Client), Part 1
The following is part 1 of a series of posts for creating an offline application using Silverlight 2.0
Introduction
Once of the alluring aspects of Silverlight is creating an application with a pretty broad reach (cross-platform/browser) using technologies familiar to the “Microsoft Developer” (C#, VB.NET, etc.) together with some common application patterns (smart clients). This series of posts is intended to plug the gap in creating a Silverlight 2.0 application that completes the “smart client” pattern with occasionally connected (read: “offline”) features.
Problem
Silverlight does have many of the aspects of a “smart client,” such as …
- Automatic/intelligent installation and update
- Broad client platform/device reach
- “Connected” to back-end services (like LOB logic)
- Use of local resources
… and some added of it’s own:
- Very small runtime size (~4 MB)
- Low client requirements (a browser)
- Declarative programming model (XAML)
- Rich UI Framework (Rich Internet Application)
However, it currently lacks formalized support for the most prominent feature of being occasionally connected. Customers, however, are unwilling to compromise and want all of the above, together, without having to learn a new platform and a set of technologies (like Flash, for example).
Silverlight 3.0 promises new features to help in implementing these new features it is not out yet (in Beta at this time) and customers may already have a need for Silverlight today or have existing application in Silverlight 2.0.
Solution
The good news is that, with one exception, Silverlight 2.0 is fully equipped to handle the offline scenario with little additional effort over what may be coming in 3.0 or what you may have today with other Smart Client or Rich Internet Application (RIA) technologies.
The following techniques will be demonstrated in the upcoming series of posts:
- Offline, persistent, secure storage: Isolated Storage
- Synchronization with back-end services
- Detecting the network and connectivity to the back-end services
- Re-launching the application while offline
Companies can create fully disconnected application today in Silverlight 2.0 and I’ll walk you thought the process in upcoming posts. If you would like to see anything specific please feel free to add some comments and I’ll try and incorporate those into subsequent posts.
Silverlight: Cloud Connected
- “Wiring” up a Silverlight 2.0 application to a bunch of services
- Demonstrations of leveraging WCF, ASP.NET Data Services/REST, XML
- How you can quickly bind data through XAML in a pain-free manner.
- A glimpse into the designer/developer workflow
- Some discussions on differences you’ll notice from WPF.
- A hands-on demo of the tools you’ll use in SL development
- Some other stuff (LINQ, Lambda expressions, type inference, blah blah blah blah)
- Working with IsolatedStorage in an attempt to have this thing work offline
Review of online game trading sites: Goozex, SaySwap, GameTZ
always an option, but we all know they have some pretty crappy trade in
prices. You could always try one of the many online game trading sites.
But, which one is best? See this review to get a better idea of what to
expect from these online game trading services….
http://adultgamingenthusiasts.com/showthread.php?7825-Review-of-online-game-trading-sites-Goozex-SaySwap-GameTZ
SOA – Service-Oriented Architecture
The agenda was:
- SOA: Definition and Rationale
- The Shift to Service-Orientation
- SOA: Best Practices
- Microsoft Solutions for SOA
Demos include:
- Contract-first using XML Schema, xsd.exe, and WSDL
- Policy-based security (WS-Security) and WSE 3.0
- Schema Rationalization/Canonicalization
- Perimeter/Referral routing using WSE and WS-Messaging (using SoapHttpRouter)
Downloads:
– SOA Slides
– Demo Code
Visual Studio Unit Testing an asynchronous event callback
Problem …
Long title … simple problem: I am writing automated unit test cases for an asynchronous method call which returns back via an event handler (a callback).
If I had architected the method that I am calling I would have used the standard Begin/End methods to handle the asynchronous calls but I am using a pre-written source code so I need to adhere to its methodology.
Solution …
Nonetheless, I needed a way to have a TestMethod make the asynchronous method call and then somehow get the results back from the event handler. I was not (am still not) aware of anything built-in to NUnit or Visual Studio Unit Testing to handle this
so I figured I was on my own.
I figured that all I really needed was a way to sleep the test method until the event handler is called and then signal it to continue and analyze the data returned from the event. Signal. I had heard that before when talking about Thread Synchronization … threading … that is what the event callback is … duh. I need a thread signal!
Enter AutoResetEvent …
Very fortunately for me, .NET has built-in just such a signal using a class called AutoResetEvent (System.Threading). Once I realized this, the code was frighteningly simple. One thread creates the signal object (initializing its state to un-signaled) and waits on it. The second thread sets the signal and the initial thread continues.
Here’s some code:
-
using System.Threading;
-
using Microsoft.VisualStudio.TestTools.UnitTesting;
-
-
namespace MyTests
-
{
-
[TestClass]
-
public class MyTestClass
-
{
-
AutoResetEvent _TestTrigger;
-
DataType _MyData;
-
-
[TestMethod]
-
public void MyTestMethod()
-
{
-
MyAsyncCall();
-
this._TestTrigger.WaitOne();
-
Assert.AreEqual(…)
-
-
}
-
-
private void My_EventHandler(…)
-
{
-
this._MyData = result from event handler;
-
this._TestTrigger.Set();
-
-
}
-
-
}
-
-
}
You can make modifications to this so that the calling method does not wait indefinitely as well as other handy mods. If you come up with anything cool please drop a comment here so everyone can share in your find!
Atlas – AJAX Programming for the .NET 2.0 Framework
- Client-Side O-O API
- Client-Side Declarative XML
- Server-Side Control Extenders
- Server-Side Partial Rendering (UpdatePanel)
For anyone that wants them … here are links to my slides and code:
For more information I recommend you check out the Atlas home page at: http://atlas.asp.net .