Welcome to Stephen's wiki. There is lots of really great content here - you just have to search for it.

This is a collection of random stuff I want to record for future reference. Probably not much use to anyone else.

1. In Visual Studio, from the main menu, select Test → Edit Test Settings → Local (Local.testsettings).
2. [Test Settings] Select the Save As button.
3. [Save As] Enter 'CodeCoverage.testsettings' and select OK.
4. [Test Settings] Select Data and Diagnostics.
5. [Test Settings] Enable Code Coverage.
6. [Test Settings] Double-click Code Coverage.
7. [Code Coverage Detail] Select the assembly or assemblies that you wish to have code coverage for. Normally this would be the non-test assemblies.
8. [Code Coverage Detail] Select OK.
9. [Test Settings] Select Apply and then Close.
10. [Save Dialog] Select Yes.
11. Done. Test settings should be checked into source control.

1. In Visual Studio, from the main menu, select Test → Select Active Test Settings → Local (CodeCoverage.testsettings).
2. Change the build configuration to Debug.
   1. From the main menu, select Build → Configuration Manager….
   2. [Configuration Manager] Set the Active Solution Configuration to Debug.
   3. [Configuration Manager] Select Close.
3. If the target is signed, temporarily remove it.
   1. Open the project properties.
   2. Select the Signing tab.
   3. Uncheck the Sign the assembly check box.
   4. Save the project.
4. Run the unit tests.
5. Turn the Code Coverage Colouring on and off in the Code Coverage Results window.

…and maintaining version history.

1. [SubVersion] Export the trunk to a temp directory.
   • C:\Temp\SuperApp\trunk
2. [Text Editor] In the temp solution, open the solution file.
   • C:\Temp\SuperApp\trunk\SuperApp.sln
3. [Text Editor] Find the section that has Web Site Project. It will look something like:

   Project("{E24C65DC-7377-472B-9ABA-BC803B73C61A}") = "SuperApp.Web", "SuperApp.Web", "{C92B633A-C441-4FB6-904B-EEA604BAAF15}"
   	ProjectSection(WebsiteProperties) = preProject
   		...
   		ProjectReferences = "{0A231AD6-AF0C-45C1-B441-2AB97BC40975}|SuperApp.DataAccess.dll;{96DC8217-C24D-4851-B4C2-92FBE60727CC}|SuperApp.Business.dll;"
   		...
   	EndProjectSection
   EndProject

4. [Text Editor] Note down any project references for later. In the example above, the Web Site Project references SuperApp.DataAccess.dll and SuperApp.Business.dll.
5. [Text Editor] Delete the entire Web Site Project (from Project to EndProject inclusive) and save.
6. [Windows Explorer] In the temp solution, delete the entire Web Site Project directory
   • C:\Temp\SuperApp\trunk\SuperApp.Web
7. [Visual Studio] Open the temp solution.
8. [Visual Studio] Create a new ASP.NET Empty Web Application in the old Web Site Project directory. Make sure it is the correct language (VB or C#)! The language of new ASP.NET Empty Web Application must match the existing Web Site Project.
   • C:\Temp\SuperApp\trunk\SuperApp.Web
9. [Visual Studio] Save and close.
10. [SubVersion] Copy and rename to a branch.
    • C:\Dev\SuperApp\trunk → C:\Dev\SuperApp\branches\Converting to Web App
11. [Text Editor] In the branch solution, open the solution file.
    • C:\Temp\SuperApp\branches\Converting to Web App\SuperApp.sln
12. [Text Editor] Remove the Web Site Project and save.
13. [Windows Explorer] Copy from the temp solution to the branch solution:
    • (C#) C:\Temp\SuperApp\trunk\SuperApp.Web\Properties → C:\Temp\SuperApp\branches\Converting to Web App\SuperApp.Web
    • (VB) C:\Temp\SuperApp\trunk\SuperApp.Web\My Project → C:\Temp\SuperApp\branches\Converting to Web App\SuperApp.Web
    • C:\Temp\SuperApp\trunk\SuperApp.Web\SuperApp.Web.csproj → C:\Temp\SuperApp\branches\Converting to Web App\SuperApp.Web
    • C:\Temp\SuperApp\trunk\SuperApp.Web\Web.Debug.config → C:\Temp\SuperApp\branches\Converting to Web App\SuperApp.Web
    • C:\Temp\SuperApp\trunk\SuperApp.Web\Web.Release.config → C:\Temp\SuperApp\branches\Converting to Web App\SuperApp.Web
14. [Text Editor] The Web.config in the branch solution probably does not need to be changed, but open both and check just in case.
    • C:\Dev\SuperApp\branches\Converting to Web App\SuperApp.Web\Web.config
    • C:\Temp\SuperApp\trunk\SuperApp.Web\Web.config
15. [Visual Studio] Open the branch solution.
16. [Visual Studio] In the Solution Explorer, turn on Show All files.
17. [Visual Studio] In the Web App project, include all the file and directories except the Bin and Obj directories.
18. [Visual Studio] Right click the Web App project and select Manage NuGet Packages.
19. [Visual Studio, Manage NuGet Packages dialog] If there is a message about restoring NuGet packages, do it.
20. [Visual Studio] Add the project references noted down in step 4.
21. [Visual Studio] Right click each ASPX file and select Convert To Web Application.
22. [Visual Studio] Set the Web App project as the start up project, and set the appropriate start page.
23. [Visual Studio] Cross fingers and run it.

<script src="../Scripts/jquery-1.7.2.min.js" type="text/javascript"></script>
<script type="text/javascript">
	$(document).ready(function () {
		$(".CollapsibleTrigger").click(function (event) {
			$(this).next().toggle();
 
			if ($(this).next().is(':visible'))
				$(this).addClass('Expanded');
			else
				$(this).removeClass('Expanded');
		});
	});
</script>

<asp:ListView ID="Foo_ListView" runat="server" DataSourceID="Foo_Logic" DataKeyNames="FooID" >
	<LayoutTemplate>
		<table class="DataWebControlStyle" cellspacing="0" cellpadding="2" border="1">
			<tr class="GridHeader">
				<th>Blah</th>
				...
			</tr>
			<asp:PlaceHolder ID="itemPlaceholder" runat="server" />
		</table>
		<asp:DataPager runat="server" ID="ContactsDataPager" PageSize="50">
			<Fields>
			<asp:NextPreviousPagerField ShowFirstPageButton="true" ShowLastPageButton="true"
				FirstPageText="|&lt;&lt; " LastPageText=" &gt;&gt;|"
				NextPageText=" &gt; " PreviousPageText=" &lt; " />
			</Fields>
		</asp:DataPager>
	</LayoutTemplate>
	<ItemTemplate>
		<tr class='<%# String.Format("{0} CollapsibleTrigger", Me.AlternatingGridRowClass()) %>'>
			<td><asp:Label ID="Foo_Label" runat="server" Text='<%# Eval("Foo") %>' /></td>
			...
		</tr>
		<tr class="CollapsibleRegion" style="Display: none;">
			<td><asp:Label ID="Bar_Label" runat="server" Text='<%# Eval("Bar") %>' /></td>
			...
		</tr>
	</ItemTemplate>
</asp:ListView>

Private _alternateRow As Boolean
Protected ReadOnly Property AlternatingGridRowClass() As String
	Get
		_alternateRow = Not _alternateRow
		Return If(_alternateRow, "GridAlternatingRow", "GridRow")
	End Get
End Property

Protected Sub Foo_ObjectDataSource_Updating(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.ObjectDataSourceMethodEventArgs) _
	Handles Foo_ObjectDataSource.Updating
 
	Dim iod As IOrderedDictionary = e.InputParameters
	For Each de As DictionaryEntry In iod
		System.Diagnostics.debug.print(de.Key & "=" & de.Value)
	Next
End Sub

ASP.NET's UpdatePanel will not work if xhtmlConformance mode is set to Legacy in the Web.config file:

<xhtmlConformance mode="Legacy" />

Take it out of the Web.config file - it almost certainly does not need to be in there.

With administrator privileges, edit the C:\Program Files (x86)\VideoLAN\VLC\lua\http\.hosts file, and set it to:

::/0
0.0.0.0/0

This will probably need to be done every time a new version of VLC is installed.

Probably caused by the Web.config file. Remove the following, if they exist:

<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
 
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere" />
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />

Removing these from the Web.config doesn't seem to matter, but if it does, try adding the relevant DLL files and see if that fixes the problem.