I first tried changing the value of maxUrlLength in my Web.config
<httpRuntimetargetFramework="4.5"maxUrlLength="2083"maxQueryStringLength="2048" />

But that didn't fix it. I was still getting a 400 response for the long url.  I did some searching and it looks like a lot of users have run into the same issue.  Unfortunately, the answer given was always to make the web.config change above, which wasn't working for me.  There were also the very unhelpful "well you shouldn't have a URL that long!" comments.  At some point, my service may need to limit how many ids it accepts or move the requested ids into the body, etc, but right now the service would be able to respond with 50 documents if it could just get the request!

After little more searching and I found that this actually requires a two part change.  In addition to the web.config value, a registry entry also has to be set to tell HTTP.sys to allow longer URLs (Imran Baloch wrote a helpful blog about this here: http://weblogs.asp.net/imranbaloch/archive/2010/04/23/understanding-400-bad-request-exception.aspx).  By default, HTTP.sys permits 255 segments at a maximum length of 260 characters each.  That 260 character limit was the cause of my issue.  So, as part of my site deployment powershell script, I need to update the value in the registry value with something like:

Set-ItemProperty -Path HKLM:\System\CurrentControlSet\Services\HTTP\Parameters -Name UrlSegmentMaxLength -Value 2000 -Type "Dword"

Now according to http://support.microsoft.com/kb/820129, to get this registry change to take effect, I need to restart the HTTP System Service by calling "net stop http" and "net start http".  But I keep running into a problem where something is blocking the HTTP system service from stopping and the service hangs. The only reliable way I have found to get this registry change to take effect is to reboot the machine (or VM).  Thus, my Azure deployment script now starts with

$regkey="HKLM:\System\CurrentControlSet\Services\HTTP\Parameters"
$regname="UrlSegmentMaxLength"
$regvalue="2000"
$regtype="Dword"
$exists= Get-ItemProperty $regkey $regname -ErrorAction SilentlyContinue
if (-not($exists) -or$exists.$regname-ne$regvalue)
{
    Set-ItemProperty- Path $regkey -Name $regname -Value $regvalue -Type $regtype
  Restart-Computer
}

And, now my service now receives the request. 

The type or namespace name 'Moles' does not exist in the namespace ... (are you missing an assembly reference?)

I thought this should be an easy fix and so I did some online searching and couldn’t find a comprehensive answer.  So I’m writing this blog for the next person who encounters this issue.

Option 1: Everyone using this solution has to install Moles

If you want to use this solution, you need to install Moles.  You’ll have to do this anyway if you’re actively working on the tests in the project.   And you’ll have to do this on your build server.  But, all your build issues regarding Moles will be solved and all your tests will run.  If you’re running BVTs that use Moles, this is your only option.  Moles has to be installed for the tests to run.

Personally, I don’t like asking people to install a lot of things on their machine they don’t actually need.  Just because Tom is actively using Moles doesn’t mean Harry should have to install it just to build the solution.  And, not everyone has full control to install whatever they’d like on their build server.

Option 2: Unload the test project

The solution will build, but this is a per-user setting.  And this doesn’t solve the failure to build on the build server.

Option 3: Modify the project references

Make a local copy of the Moles dlls shipped in Moles referenced in your project and manually edit the project references to point to your local copy

For example, change:

<Reference Include="Microsoft.Moles.Framework, Version=0.94.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL" />

To

<Reference Include="Microsoft.Moles.Framework">     
<HintPath>$(SolutionDir)External\MolesAssemblies\Microsoft.Moles.Framework.dll</HintPath>
</Reference>

And for the dlls generated by Moles – for example I have a Mole for my Msn.TomsFramework class with the following reference:

<Reference Include=" Msn.TomsFramework.Moles, Version=1.0.15336.204, Culture=neutral, processorArchitecture=MSIL"/>

I don't want to use a HintPath for these because I'll break the project for users actively working on the project with Moles.  Instead, I copied an instance of the generated dll (Msn.TomsFramework.Moles.dll) alongside the Moles definition file (Msn.TomsFramework.moles).  I store these in my $(SolutionDir)Moles directory.

And I added a BeforeBuild target to my project file to copy all those dlls to the bin folder so the project can find the references and build

<Target Name="BeforeBuild">   
<ItemGroup>
<MolesDLLsToBeCopied Include="$(SolutionDir)Moles\*.dll" />
</ItemGroup>
 <Copy SourceFiles="@(MolesDLLsToBeCopied)" DestinationFolder="$(OutDir)" ContinueOnError="true" />
</Target>

updated for MSBuild for .NET 4 (Thanks, Shaun!)

  <Target Name="CopyMolesGeneratedTypes" BeforeTargets="BeforeBuild">
    <ItemGroup>
      <MolesDLLsToBeCopied Include="$(SolutionDir)Moles\*.dll" />
    </ItemGroup>
    <Message Importance="high" Text="Copying generated types for Moles" />
    <Copy SourceFiles="@(MolesDLLsToBeCopied)" DestinationFolder="$(OutDir)" ContinueOnError="true" />
  </Target>

Now this project builds on my machine and the build server without having Moles installed.  It is important to note that the tests do not pass as Moles requires GAC-ed assemblies to run correctly.  So if you can’t install Moles on your build server, you’ll want to remove the Moles tests from your BVTs.

[02/10/10,18:18:55] Microsoft Silverlight: [2] Error code 1502 for this component means "The event log file is full.
[02/10/10,18:18:55] Microsoft Silverlight: [2] Component Microsoft Silverlight returned an unexpected value.
[02/10/10,18:18:55] Microsoft Silverlight: [2] Return from system messaging: The event log file is full.

CAUSE:

There are two versions of the Silverlight runtime: The end user runtime and the developer runtime which contains a managed debugging component that allows developers to debug their Silverlight applications.

Silverlight recently released an update on Microsoft Update to the runtime to support features you’ll see on the web broadcast of the Winter Olympic Games.  Updates were released for both the end user and developer runtimes.

Visual Studio 2010 RC has a slightly older release of the dev runtime included.  If only the end user runtime is installed, during VS installation, it detects that the managed debugging component is missing and attempts to install the dev runtime.  However, because the newest end user runtime is already installed, installation fails.  (And the error code is misinterpreted to mean that the event log is full.

SOLUTIONS:

This issue was recently fixed, but after the final build of VS2010 RC was released, so it will be in the RTM release.  In the meantime…

If you’re not a Silverlight developer, go ahead and ignore this message.  Your installation of Visual Studio is not affected.

If you are a Silverlight Developer, you can download and install the latest version of Silverlight 3 Developer Runtime or the Silverlight 4 Beta Developer Runtime so that you can debug your Silverlight projects.

Some things you should know...

Silverlight 4
Support for Silverlight 4 development requires a separate add on which is not immediately available for VS2010 RC.  If you're doing Silverlight 4 Beta development, stick with VS2010 Beta 2 for now.  http://blogs.msdn.com/wpfsldesigner/archive/2010/02/09/silverlight-support-for-visual-studio-2010-release-candidate.aspx

MVC 2
VS2010 RC ships with MVC2 RC1.  But you may have heard that MVC just released an RC2.  If you want to use MVC RC2 with VS2010 RC, uninstall the MVC2 _RUNTIME_ (NOT the TOOLS) and install the MVC RC2. http://haacked.com/archive/2010/02/04/aspnetmvc2-rc2.aspx

Possible Setup Issues
Silverlight Runtime - If you get an install failure with the Silverlight runtime that "event log is full", the Silverlight developer runtime included with VS2010 failed to install because you have a newer version of the Silverlight end user runtime installed.  Yes, the error message doesn't explain that.  You can get the latest developer runtime (which includes the managed debugging component required to debug Silverlight projects) from http://go2.microsoft.com/fwlink/?LinkID=150228

Feedback
Tell us what you think so we can make any fixes before the release to manufacturers...

• Report a Bug through Connect: https://connect.microsoft.com/VisualStudio/?wa=wsignin1.0
• Fill out the VS2010 Survey: https://mscuillume.smdisp.net/Collector/Survey.ashx?Name=VS2010-RC
• Give feedback on Twitter by using tags like #VS2010 #fail #awesome etc

Silverlight 3 Tools for Visual Studio 2008 and Expression Blend 3 included SDK build 3.0.40624.

Silverlight 3 SDK build 3.0.40818 cannot be installed on machine where build 3.0.40624 is already installed. If you install Visual Studio 2010 on a machine that already has build 3.0.40624 installed, Visual Studio 2010 will indicate that the Silverlight 3 SDK failed to install, however you will still be able to do Silverlight development on Visual Studio 2010 with build 3.0.40624.

Silverlight 3 SDK build 3.0.40818 contains the following updates:

• Remove dependency on .NET 3.5 and allow build when only .NET 4 is installed
• Support for use of non-unicode characters in xap name
• Improvements to refactoring and intellisense

To get build 3.0.40818of the Silverlight 3 SDK, uninstall Silverlight 3 SDK build 3.0.40624 from Add/Remove Programs and then install Silverlight 3 SDK build 3.0.40818 from: http://go2.microsoft.com/fwlink/?LinkID=157102.

One of the prerequisites for Silverlight 3 Tools for Visual Studio is the installation of the Visual Web Developer feature in Visual Studio 2008 SP1.  This is separate from the free Visual Web Developer Express. If VWD is not already installed with your instance of Visual Studio, you can add the feature in Visual Studio's Maintenance Mode.

Open Add/Remove Programs from the Control Panel. Right click on Visual Studio 2008 and choose Remove/Change.

This will bring up Maintenance Mode.  On the second screen, Choose Add or Remove Features.

Check the box next to Visual Web Developer (also, make sure you Visual C# and/or Visual Basic also installed) and click the Update button.

Once the installation is complete, you can install Silverlight 3 Tools for Visual Studio 2008

When the Silverlight Tools fail to install, a log file is generated with error codes and messages.  You can open this log file from the last screen of the installer.  Or, you can find this log file in your %TEMP% directory under the name  Silverlight Tools RTW_[installation date and time].html or Silverlight 3.0 Tools_[installation date and time].html

 
Silverlight Tools Installer

Web Platform Installer

Open this log file and look at the end to find the exit code and messaging about why the installer failed.  It may say something like “Final Result: Installation failed with error code: (0x80072EE5).” or “Final Result: Installation failed with error code: (0x1), Incorrect function.”

<param name="minRuntimeVersion" value="3.0.40307.0" ...

<asp:Silverlight MinimumVersion="3.0.40307.0"  ...

In addition, if you use an object tag, make sure to update the link to install the newest runtime to: http://go.microsoft.com/fwlink/?LinkID=141205