Anith Gopal

On WCF forums, I have noticed a common issue that developers face when hosting their WCF service in WAS. The issue is that the service does not get activated. Often, the reason is that the queue name does not match the service endpoint name.

Once I had the event aggregator set up in GenesisEngine I could think about how to turn keyboard and mouse input into events that other parts of the app could respond to. The XNA framework doesn’t offer as much help in this area as you might be used to in Windows Forms or WPF.  There isn’t any built-in windowing, or UI controls, or a commanding system so you pretty much have to build your own from scratch.  This isn’t a terribly difficult task, I suppose, but I like the way mine turned out. XnaInputState All XNA offers for input is a KeyboardState and MouseState struct every update cycle that contain the current state of the keyboard (the current up or down state of every key) and the current state of the mouse cursor (where it currently is and whether each button is currently up or down)

  There are a lot of timeouts in WCF. let us summarize it here.

Pre-Requisites: You will need some experience using the Business Rules Composer (some basic staff is taken for obvious) Benefits: There is no need to call a .NET component with SQL database helper functions or whatever Business rules engine will catch the results. If the requirement change, you can adapt the business rules on the fly with no need to redeploy the orchestration

  Introduction This article introduces some common Windows Forms scenarios. The samples are from the All-In-One Framework, and it is only a portion of the All-In-One Framework

IIS 7 allows isolation of web application pools from each other by providing the ability to run application pools as separate identities. The identity of an application pool is the name of the service account under which the application pool’s worker process runs. Running an application pool under an account that has high-level user rights is a serious security risk.

[Part 3 of the FScheme series ]   Continuing along in Bill Hails’ book .

A common problem in writing test automation against an API is that you need to be able to load the assemblies containing the code under test (CUT) into the test process.  There are several options which have been employed in the past to ensure that it is possible to load these assemblies including copying the CUT assemblies next to the test assemblies, copying the test assemblies next to where the CUT assemblies are deployed before running the tests, and setting up custom assembly resolvers.  Each of these has their drawbacks when you start trying to execute your tests in different environments.  For example copying the CUT assemblies next to the tests may work great on your development machine, but when you want to also run these tests in a lab against the installed product a better solution is needed.  In VS 2010 we have incorporated an assembly resolution solution directly into the unit test framework which will allow you to easily configure where the dependencies of your tests get loaded from. The assembly resolution settings can be configured by opening up Test Settings and navigating to the “Unit Test” section.  Below is a screenshot of the settings for reference as we go through what each of them are for: These assembly resolution settings will be used for all tests that are executed in the run and will override any assembly resolution settings which were put into the test projects App.Config file (more later in this post about the assembly resolution settings that can be put into the App.Config file).

Posting some answers to questions I’ve gotten recently. Bug in the samples: Kind of silly that I hadn’t noticed this until now, but there’s an error in the sample html for most of the samples.  The name of the functions used for plug-in load and activate conflict with an internal name used in the AJAX code.  Change “On3DPlugInLoaded” and “On3DPlugInActivated” to any other name, for example “PlugInLoaded” and “PlugInActivated”.  Remember to change both your function name and the string passed to AttachEvent.

Client Certificate Mapping – Step by Step – Table of Content   In this post, we will create FTP Site on IIS and configure it to use Client Certificate.

I just released an update to VsVim for Visual Studio 2010 Beta2.  This should be available shortly from the extension manager in Visual Studio or it can be downloaded directly at the following link Link: http://visualstudiogallery.msdn.microsoft.com/en-us/59ca71b3-a4a3-46ca-8fe1-0e90e3f79329 Changes Removal of conflicting key bindings On startup VsVim will now look for any key bindings which conflict with implemented Vim commands. It will then provide a message box allowing you to remove the key bindings for this session of Visual Studio. Right now this is an all or nothing removal, future versions may make this a more granular process Normal Mode no longer intercepts all keystrokes (such as Cut and Paste) This bug in the previous release was a result of the command routing changes that occured between Beta1 and Beta2

Support for the WCF net.tcp protocol is the key feature addition in the core of WCF offering in Silverlight 4 Beta. Read more about the benefits and limitations of the net.tcp protocol in Silverlight 4 to decide if it is a good fit for your application