XmlDocument readTable = new XmlDocument();Refer XPath Examples for the syntax of more kinds of searches you can do.
readTable.LoadXml(stringXml);
int rowCount = readTable.SelectNodes("Table/Row").Count;
When you are writing a Windows application, the ubiquitous MessageBox is extremely useful for popping up a quick debug message but it’s not available for ASP.NET Web Forms.
In such cases, use:
Response.Write("<script language='javascript'>alert('Your message');</script>");Enjoy!
if "%MSDeployPath%" == "" (
for /F "usebackq tokens=1,2,*" %%h in (`reg query "HKLM\SOFTWARE\Microsoft\IIS Extensions\MSDeploy" /s ^
findstr -i "InstallPath"`) do (
if /I "%%h" == "InstallPath" (
if /I "%%i" == "REG_SZ" (
if not "%%j" == "" (
if "%%~dpj" == "%%j" (
set MSDeployPath=%%j
))))))
Dates are a PIA – no matter what language.
Found a neat way to do the validation e.g. the d/m/yyyy vs. d/mm/yyyy vs. dd/mm/yyyy etc.
bool validDate = DateTime.TryParseExact(txtDate.Text,
new[] { "dd/MM/yyyy", "d/MM/yyyy"},
CultureInfo.InvariantCulture, DateTimeStyles.None, out d);
if (!validDate)
{
Error stuff
}
else
Valid stuff
So you just add the valid patterns to the array and away you go!
Enjoy!
c:
cd\Inetpub\AdminScripts
cscript adsutil.vbs enum w3svc/1
C:\inetpub\wwwrootYou should now have it back - along with others that may have been in that directory.
Over on the TechNet Wiki, I contributed an article on a Kerberos Survival Guide.
Just been notified that:
The article Kerberos Survival Guide on the TechNet Wiki has achieved its 15 minutes of fame. Congratulations!
To clarify:
As you can see here: How do I earn points?, the points you get range between 5 and 2,500 points when your article gets from 500 to 1 million page views. "15 minutes of fame" is the first milestone.
Enjoy!
I do a lot of work developing applications on my Windows 7 32 bit machine using IIS 7.5 and then migrating them to IIS 7.5 on my Windows Server 2008 R2 64 bit box. Not as simple as it sounds.
Using VS 2010, my DefaultAppPool on Windows 7 uses the .NET 4.0 framework whereas it’s 2.0 on Windows 2008. So you need to make a new application pool and set it to “Integrated” and the 4.0 framework.
OK – then I get the above error. The blurb below on the error page says that the most likely cause is that:
“Managed handler is used; however, ASP.NET is not installed or is not installed completely.”
Check my installed features in IIS 7.5 and Yup – ASP.NET is installed, it has a handler etc. So WTF?
Mr. Google to the rescue.
Run a command prompt in administrative mode.
C:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis.exe -i
Start installing ASP.NET (4.0.30319).
..................
Finished installing ASP.NET (4.0.30319).
Note: Your version of the framework may be different!
Notice that it installs ASP.NET even though it is already supposed to be there but it fixes the problem and all is well!
Enjoy!
Playing around with WCF web services in VS 2010 and .NET Framework 4.
When I run the WCF Test Client across the web service I get the above error. The service still works but there’s an error symbol (a ! in a red circle on the LHS).
Mr. Google to the rescue and you need to change the framework config file here:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
Comment out the “endpoint” section i.e.
<client>
<!-- <endpoint address="" binding="netTcpRelayBinding" contract="IMetadataExchange" name="sb" /> -->
<metadata>
Problem solved.
Even though it still works, I hate these niggly errors in case I’ve screwed up
Enjoy!
<html>
<body>
<h1>ASP Request Variables Page</h1>
<h2>
The current user you are logged in as is:
<u>
<!-- <%=Request.ServerVariables("AUTH_USER" & "<br />") %> -->
<%= response.write("AUTH_USER" & " " & Request.ServerVariables("AUTH_USER") & "<br /><br />") %>
<u>
</h2>
<%
for each x in Request.ServerVariables
response.write(x & " " & Request.ServerVariables(x) & "<br /><br />")
next
%>
</body>
</html>
There’s an amazing amount of tools “hidden” on your PC that you probably aren’t even aware off 
A lot of them are stored in the
C:\Program Files\Microsoft SDKs\Windows
directory. These mainly derive from the Windows SDK for Windows 7 and .NET Framework 4.
Browse through StartTools.htm located at:
C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin
There’s an amazing collection of tools there.
The actual binaries are located here:
C:\Program Files\Microsoft SDKs\Windows\v7.0A\bin
To quote:
“The Windows SDK tools are designed to make it easier for you to create, deploy, and manage applications and components that target Windows and the Internet. The Windows SDK includes tools for both the .NET 3.5 SP1 and 4 Frameworks - a managed programming model - and tools for Win32® - the native (unmanaged) programming model for Windows. Many of the Windows SDK tools are listed on this page and categorized by target audience: managed, native and "common" (tools that could be used by either managed or native developers).”
Enjoy!
PowerShell is command line which means that you lose out on all the benefits that an IDE brings.
There is an in-built PowerShell IDE:
Just type “ise” from the command line
but it’s pretty basic.
Then I came across PowerGui.
It has two parts viz. an administrative console that allows you to run a collection of PowerShell scripts and a script editor that allows you to enter and run scripts. It has intellisense and a set of built in snippets. It has a debug function where you can step through the script and examine all the variables.
Very neat – and BTW it’s free.
Enjoy!
SPN stands for Service Principal Name – used (among others) by Kerberos.
Normally, you work with them via the Setspn tool.
e.g.
setspn –l <account name>
which lists all spns assigned to that account.
However, you can also do this by:
Start – Administrative Tools – Active Directory Users and Computers – View – Advanced Features
Then navigate to the account via the tree. Right click – Properties – Attribute Editor tab. Then scroll down to servicePrincipalName and double-click.
You can add and remove SPN’s from this window as well. (i.e. the equivalent of setspn –a … or setspn –d …).
Enjoy!
If you are using WIF and C2WTS and you get the above error, it’s probably because the C2WTS service is not yet started.
It’s this one in the Services windows (which is in the “Administrative Tools” menu):
“Claims to Windows Token Service”
and the description is:
“Service to convert claims based identities to windows identities”
Note that you must use Windows domain user accounts. These accounts must have a Universal Principal Name (UPN).
Enjoy!
A number of people have commented on this problem with ADFS v2.0. It seems to be confined to Internet Explorer (IE).
Basically, the problem is that you want to display a site’s metadata so you browse to the URL (the https://xxxx//FederationMetadata/2007-06/FederationMetadata.xml one) and see … zip / nada / nothing / blank. WTF!
Two “solutions” that may help:
Enjoy!
When you’re in ADFS v2.0 and you are trying to update the metadata of a CP or RP, you sometimes get the “An error occurred during an attempt to read the federation metadata” message.
A useful trick is to open a browser and navigate to the URL of the site whose metadata you are attempting to update. If you get any certificate errors, fix them first. ADFS does not like certificate errors. Everything has to be squeaky clean!
Enjoy!
It’s a common problem with IE. You access a site and get a certificate error and get the pink address bar when you access the site. The solution is to install the certificate into the “Trusted Root CA” certificate store.
You normally do that by clicking the padlock icon to the right of the address bar then “View Certificates” and then clicking the “Install Certificate” button. Lately, I've come across some instances where the button is missing in action. WTF?
Mr. Google to the rescue and the solution is to right-click the IE icon on the desktop and select “Run as administrator”. (In other words, IE needs to be run as Administrator).
And then there was sweetness and light and verily the button doth appear!
Enjoy!
ADFS either uses SQL Server or an WID to store all the configuration components. I’ve tried before to access the WID with no joy but then discovered that the reason why was because of the completely non-intuitive and obtuse server name which has to be:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
Damn, why on earth didn’t I think of that?!
The easiest way to access it is via the free SQL Server Management Studio Express. Ignore all the talk of SQL Server 2005 Express Edition – it works for the WID.
When you connect, leave the “Server Type” as “Database Engine” and insert the above string as the “Server Name”.
Away you go – the two DB of interest are AdfsArtifactStore and ADFSConfiguration.
Enjoy!
Needed to do some work in this area and found the following extremely useful:
KerbTray is a GUI tool used to display ticket information for a given computer running the Kerberos protocol. You can purge all the Kerberos tickets with this.
KList is a DOS prompt tool used to view and delete the Kerberos tickets granted to the current logon session. It allows you to delete selected Kerberos tickets (as opposed to KerbTray which deletes them all).
In terms of debugging, I found Wireshark to be useful to see what happens on the actual wire. You can sort the packets by using the Kerberos protocol as a filter.
The other alternative is to enable Kerberos event logging. Really simple to do – just one registry setting. Just remember to disable it when you are done.
DelegConfig is an ASP.NET application used to help troubleshoot and configure IIS and Active Directory to allow Kerberos and delegated Kerberos credentials. It can be really useful but has to be setup correctly. Worth running if only to read the comments and explanations.
Enjoy!
Trace or log files are very useful to help you find problems with WIF.
I normally add the following to the end of the web.config.
<system.diagnostics>
<sources>
<source name="Microsoft.IdentityModel" switchValue="Verbose">
<listeners>
<add name="xml" type="System.Diagnostics.XmlWriterTraceListener"
initializeData="xxx\Logs\WIF.xml" />
</listeners>
</source>
</sources>
<trace autoflush="true" />
</system.diagnostics>
</configuration>
This produces a ton of output in XML format but it's not that easy to read it!
The trick is to use the Service Trace Viewer Tool.
See Examining WCF Diagnostic Traces Using Service Trace Viewer Tool for download instructions.
Run up the tool (you may need to run as administrator), then File / Open with the file type set to XML and you'll find it so much easier!
Enjoy!
The Internet is a wonderful source of information – the only problem is at least half of it is rubbish and a quarter of the rest is misleading.
Had an example of this recently on a forum.
I was asking about V2 of a product and the answer was “Look at this article”. Which I duly did and noticed that the article referred to V1 of the product which used a feature which had been removed in V2.
I pointed that out on the forum. Back comes the answer “Oh – just ignore that section” WTF – without that section there is no solution.
Pointed that out on the forum. Back comes the answer “Find a similar article” WTF – that’s where I started. I couldn't find one – hence the forum question.
Thanks for FA dude!
Enjoy!
There’s really useful information out there on the forums.
If everything turns to custard when you are trying to customise ADFS, you can always re-install.
A quicker way is to know that a copy of the original installation is found at:
…\Program Files\Active Directory Federation Services 2.0\WSFederationPassive.Web
Simply copy it over to:
…\inetpub\adfs\ls
Thanks to Steve Syfuhs for this tip.
Enjoy!
<system.web> <pages validateRequest="false" /> <httpRuntime requestValidationMode="2.0" /> ...
Originally when I registered with MSDN I used my normal name (nzpcmad). Moved on to other areas and when I wanted to use MSDN again, I found that things had changed. When I updated my profile, I was informed that the name “nzpcmad” was already in use (WTF – I know that!) and hence was forced to choose a new name “nzpcmad1”.
So just to confirm:
nzpcmad = nzpcmad1 = Me
Enjoy!
Something in the nature of an experiment. Setting up Windows Live Writer so I can contribute to the TechNet Wiki (my name there is nzpcmad1) so thought I would try to my actual blog.
Enjoy!
...\Reflector7>PluginConverter.exe Reflector.CodeSearch.dll 7.0.0.0
Reflector plugin converter - Sebastien LEBRETON (reflexil.net)
Backuping Reflector.CodeSearch.dll to Reflector.CodeSearch.dll.bak
Reading Reflector.CodeSearch.dll
Found version 5.0.0.0, patching to 7.0.0.0
Writing Reflector.CodeSearch.dll
A passive client enters a shop, and starts looking around.
A salesperson approaches: "Sir, can I help you?"
And the passive client: "Just browsing."
C:\Windows\system32>net stop adfssrv
The AD FS 2.0 Windows Service service is stopping.
The AD FS 2.0 Windows Service service was stopped successfully.
C:\Windows\system32>net start adfssrv
The AD FS 2.0 Windows Service service is starting........
The AD FS 2.0 Windows Service service was started successfully.
//public const string AcsHostName = "accesscontrol.windows.net";
public const string AcsHostName = "accesscontrol.appfabriclabs.com";
private string GetTokenFromACS()
{
var client = new WebClient();
WebProxy proxy = new WebProxy("1.2.3.4", 1234);
proxy.BypassProxyOnLocal = true;
proxy.UseDefaultCredentials = true;
client.Proxy = proxy;
client.BaseAddress = string.Format("https://{0}.{1}", this.serviceNamespace,
Constants.AcsHostName);
...
}
C:\>netsh /?
Usage: netsh [-a AliasFile] [-c Context] [-r RemoteMachine] [-u [DomainName\]Use
rName] [-p Password | *]
[Command | -f ScriptFile]
The following commands are available:
Commands in this context:
? - Displays a list of commands.
add - Adds a configuration entry to a list of entries.
advfirewall - Changes to the `netsh advfirewall' context.
branchcache - Changes to the `netsh branchcache' context.
bridge - Changes to the `netsh bridge' context.
delete - Deletes a configuration entry from a list of entries.
dhcpclient - Changes to the `netsh dhcpclient' context.
dnsclient - Changes to the `netsh dnsclient' context.
dump - Displays a configuration script.
exec - Runs a script file.
firewall - Changes to the `netsh firewall' context.
help - Displays a list of commands.
http - Changes to the `netsh http' context.
interface - Changes to the `netsh interface' context.
ipsec - Changes to the `netsh ipsec' context.
lan - Changes to the `netsh lan' context.
mbn - Changes to the `netsh mbn' context.
namespace - Changes to the `netsh namespace' context.
nap - Changes to the `netsh nap' context.
netio - Changes to the `netsh netio' context.
p2p - Changes to the `netsh p2p' context.
ras - Changes to the `netsh ras' context.
rpc - Changes to the `netsh rpc' context.
set - Updates configuration settings.
show - Displays information.
trace - Changes to the `netsh trace' context.
wcn - Changes to the `netsh wcn' context.
wfp - Changes to the `netsh wfp' context.
winhttp - Changes to the `netsh winhttp' context.
winsock - Changes to the `netsh winsock' context.
wlan - Changes to the `netsh wlan' context.
The following sub-contexts are available:
advfirewall branchcache bridge dhcpclient dnsclient firewall http interface ips
ec lan mbn namespace nap netio p2p ras rpc trace wcn wfp winhttp winsock wlan
To view help for a command, type the command, followed by a space, and then type ?.
C:\>netsh winhttp /?
The following commands are available:
Commands in this context:
? - Displays a list of commands.
dump - Displays a configuration script.
help - Displays a list of commands.
import - Imports WinHTTP proxy settings.
reset - Resets WinHTTP settings.
set - Configures WinHTTP settings.
show - Displays currents settings.
To view help for a command, type the command, followed by a space, and then type ?
C:\>netsh winhttp show proxy
Current WinHTTP proxy settings:
Direct access (no proxy server).
C:\>netsh winhttp set proxy /?
Usage: set proxy [proxy-server=][bypass-list=]
Parameters:
Tag Value
proxy-server - proxy server for use for http and/or https protocol
bypass-list - a list of sites that should be visited bypassing the
proxy (use "" to bypass all short name hosts)
Examples:
set proxy myproxy
set proxy myproxy:80 ";bar"
set proxy proxy-server="http=myproxy;https=sproxy:88" bypass-list="*.foo.com"
http://localhost:8000/ServiceModelSamples/Service
svcutil.exe http://localhost:8000/ServiceModelSamples/Service?wsdl
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ "
class Dummy : IClaimsIdentity
{
}
class ICII : IClaimsIdentity
{
IClaimsIdentity IClaimsIdentity.Actor
{
get
{
throw new NotImplementedException();
}
set
{
throw new NotImplementedException();
}
}
SecurityToken IClaimsIdentity.BootstrapToken
{
get
{
throw new NotImplementedException();
}
set
{
throw new NotImplementedException();
}
}
ClaimCollection IClaimsIdentity.Claims
{
get { throw new NotImplementedException(); }
}
IClaimsIdentity IClaimsIdentity.Copy()
{
throw new NotImplementedException();
}
string IClaimsIdentity.Label
{
get
{
throw new NotImplementedException();
}
set
{
throw new NotImplementedException();
}
}
string IClaimsIdentity.NameClaimType
{
get
{
throw new NotImplementedException();
}
set
{
throw new NotImplementedException();
}
}
string IClaimsIdentity.RoleClaimType
{
get
{
throw new NotImplementedException();
}
set
{
throw new NotImplementedException();
}
}
string System.Security.Principal.IIdentity.AuthenticationType
{
get { throw new NotImplementedException(); }
}
bool System.Security.Principal.IIdentity.IsAuthenticated
{
get { throw new NotImplementedException(); }
}
string System.Security.Principal.IIdentity.Name
{
get { throw new NotImplementedException(); }
}
}
<configuration>
<system.net>
<defaultproxy enabled="true" usedefaultcredentials="true">
<proxy bypassonlocal="True" usesystemdefault="True">
</proxy></defaultproxy>
</system.net>
</configuration>
USAGE:
SELFSSL7.EXE [/N cn=name] [/K size] [/V days] [/T] [/I] [/S name] [/A I
PAddress] [/P port] [/X] [/F file] [/W password] [/Q]
CERTIFCATE PARAMETERS:
/N name Specifies the common name(s) of the certificate.
Computer name is used if not specified.
Example: /N cn=m1.contoso.com or /N cn=m1.contoso.com;cn=m2.contoso.com
/K size Specifies the key length. Default is 1024.
/V days Specifies the validity of the certificate in days.
Default is 30 days.
TRUST PARAMETERS:
/T Adds the self-signed certificate to user's "Trusted Certificates" list.
IIS PARAMETERS:
/I Add SSL binding to IIS.
Use with the following parameters:
/S name Specifies the name of the site. Default is "Default Web Site".
/A IP Specifies the IP address for the IIS binding. Default is *.
/P port Specifies the SSL port. Default is 443.
EXPORT PARAMETERS:
/X Export certificate to PFX file.
Use with the following parameters:
/F PFX file location.
/W password for PFX file.
OTHER PARAMETERS:
/Q Overwrites existing SSL binding and/or PFX file.
The default behavior is equivalent with:
selfssl7.exe /N cn="machine name" /K 1024 /V 30
/I /S "Default Web Site /P443 /A * /T
Could not find default endpoint element that references contract 'ICalculator' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.
svcutil.exe http://localhost/IISHostedCalc/service.svc?wsdl