PDC BOF: Will cloud computing change your life?

PDC BOF: Will cloud computing change your life?

I’m going to be participating in one of the lunchtime BOF’s at PDC this year.  We’ll be talking about cloud computing and the likelihood of it changing your life in the future.  Here’s the description from the PDC BOF website:

“Cloud Computing” is a reality and is changing the technology industry. Your professional life will be impacted whether you choose a solution from Amazon, Google, Microsoft, or others.

  • How quickly will it change the economic paradigm of companies and their priorities?
  • How much will you have to learn?
  • What new opportunities will arise?
  • How soon will it affect your job?

You will benefit from this special discussion whatever your role is in the technology world.

Hope to see you at PDC.  Be sure to stop by the Pluralsight booth and grab a t-shirt.

My .NET Rocks interview on building a real cloud app

My .NET Rocks interview on building a real cloud app

You can now download my latest .NET Rocks interview on building a real cloud app. During the interview we discussed how we used a cloud computing strategy here at Pluralsight to build out our Pluralsight On-Demand! online training system. We were able to touch on many of the interesting business issues around cloud computing, including the economics, what makes sense and what might not. We also spent some time talking about the differences between the Amazon and Microsoft cloud computing platforms and the key strengths of each company.

PDC & Source Code for ESB Toolkit How To Videos

Since I started releasing the ESB Toolkit how-to videos, I’ve had several people ask me for the source code for all of the components I demo’d. Well, it took me way to long to get them packaged up, but here they are finally. I’ve packaged up everything that I used during the demos and it should be fairly straight forward for you to install it. There is an installation guide (Word 2007 format) contained in the attached ZIP archive that walks you through the install process.


The reason that I finally got around to getting this done is that my examples are now going to be used for the hands-on-labs at PDC 2009. If you want to get some hands on experience with the ESB Toolkit, drop by the Hands-On-Labs area of PDC and you will be able to work through the same projects that I have demo’d in the ESB Toolkit How-To series. 


Cheers and keep on BizTalking


Peter

Unable to deploy the MSI Application that contains WCF bindings to BizTalk

I have seen few customers running into this issue. This forced me to write this blog.


Background: On a development environment, my customer had a BizTalk application. Application has few WCF bindings. They created MSI file that can be used to install the application onto production machines. When they try to deploy the application to target machines, following error is encountered


Validation failed for 1 resource(s).


Invalid URL “http://localhost:90/” provided as destination location. Valid format of URL is “http://localhost[:port]/path“.


 


Environment: BizTalk 2006, Windows 2003


Cause: During the deployment of MSI application, For WCF bindings, BizTalk would verify whether URL is in <http://localhost[:port]/path> format or not. If it is not in the specified format BizTalk would display the error similar to the above.


 


In this specific case WCF service is hosted directly under root directory (under localhost) and hence it is referenced by http://localhost. When BizTalk checks the URL it finds that actual URL is not represented in http://localhost[:port]/path format (because it expects to see that WCF service is hosted under a Virtual directory, but not under root directly) and it errors out.  


 


Resolution: You can work around this issue by following the below steps.


 


1) In the source machine host WCF service under virtual directory (i.e. For


example instead of hosting WCF service directly under localhost host it under localhost/WCFService)


2) Modify the receive location properties of WCF Receive port and specify the modified URI. It should be like /virtualdirectoryname/servicename.svc.


3) Export the package now


4) Make sure while exporting, under the “Specify IIS Hosts” window make sure Hostname is set to localhost and Path should contain /virtualdirectoryname (If we just have “/” here it would error out)


5) Import the MSI file in the target computer


 


 


Hope this helps!