Category: Microsoft

Web Service Reference in Visual Studio 2010

If you’ve used Visual Studio 2008 or 2010, you’ll notice that Web Reference is no longer there (like in VS 2005 and previous), instead, you see Service Reference –– actually, it’s STILL there, just hidden!

So, what’s the difference?  Well, according to this post:

Add Web Reference is the old-style, deprecated ASP.NET webservices (ASMX) technology (using only the XmlSerializer for your stuff) – if you do this, you get an ASMX client for an ASMX web service. You can do this in just about any project (Web App, Web Site, Console App, Winforms – you name it).

Add Service Reference is the new way of doing it, adding a WCF service reference, which gives you a much more advanced, much more flexible service model than just plain old ASMX stuff.

So, how do you access it?  Simple — right-click on Service References in the Solution Explorer window and…

image

Click on “Advanced…”

image

Then click on “Add Web Reference…”

image

Voila!  You can now consume the web service like you did pre-Visual Studio 2008 era.  Happy coding!

How to fix a corrupted Windows 7 profile

  1. Log on with newly created administrative account.
  2. Delete C:\Users\%username%
  3. Delete C:\Users\TEMP
  4. Delete the registry key matching your SID from: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList
  5. Check the value of ProfileImagePath so the system will your correct profile.
  6. Restart once again and login with your own account.

Windows 7 Services modified and stopped

Adding this for reference, in case, I need to activate/revert on my workstation.

  • Application Experience
  • Computer Browser
  • Desktop Window Manager Session Manager (for Aero theme)
  • Diagnostic Policy Service
  • Distributed Link Tracking Client
  • IP Helper
  • Offline Files
  • Portable Device Enumerator Service
  • Protected Storage
  • Remote Registry
  • Server
  • SSDP Discovery
  • Tablet PC Input Service
  • TCP/IP NetBIOS Helper
  • UPnP Device Host
  • Windows Error Reporting Service
  • Windows Media Center Service Launcher

Most Common ASP.NET Support issues

Below is a summary of the “two top things that cause trouble in production ASP.NET web sites,” per Scott Hanselman, which he obtained from deep within Microsoft Developer Support.  Go here to read the complete article.

#1 Issue – Configuration

Seems the #1 issue in support for problems with ASP.NET 2.x and 3.x is configuration. 

Symptoms Notes
OOM
Performance
High memory
Hangs
Deadlocks 		There are more debug=true cases than there should be.

 

#2 Issue – Problems with an External (non-ASP.NET) Root Cause

Sometimes when you’re having trouble with an ASP.NET site, the problem turns out to not be ASP.NET itself.

Issue Product Description Symptoms Notes
Anti-virus software All Anti-virus software is installed onto Servers and causes all kinds of problems.
  • Application restarting
  • Slow performance
  • Session variable are null
  • Cannot install hotfix
  • Intermittent time outs
  • High memory
  • Session lost
  • IDE Hangs
  • Deadlocks

This consists of all AV software reported by our customers. All cases do not report the AV software that is being used so the manufacturer is not always known.

KB821438, KB248013, KB295375, KB817442
3rd party Vendors All This is a category of cases where the failure was due to a 3rd party manufacturer.
  • Crash
  • 100% CPU
  • High memory
  • Framework errors
  • Hang
The top culprits are 3rd party database systems, and 3rd party internet access management systems
Microsoft component All Microsoft software
  • Intermittent time outs
  • High memory
  • Deadlocks
  • 100% CPU
    Crash
Design issues that cause performance issues like sprocs, deadlocks, etc. Profile your applications and the database! (Pro tip: select * from authors doesn’t scale.) Pair up DBAs and programmers and profile from end to end