Posts tagged ‘Visual Studio 2010’

Visual Studio Fix: Intellisense Not Popping Up or Not Working

(Update 4/27/2015 Added intellisense failure)

I was running the latest version of Visual Studio 2013 and ran into the intellisense not automatically popping up when I would type a period. Now I could hit CTRL-J (list members) and it would pop up the list which showed me that it worked and was not dead per se, but I still did not have it automatically popup after typing a period. I was also running Visual Studio 2012 on the same box and it did not have the same problem; intellisense popped the list up on the period. I thought, “This ends here” and researched it. Here is what made it auto pop for me:

  1. In quick launch type “Statement Completion” and choose the first one  “Text Editor -> All Languages -> General” to be taken to the options page for all languages.
  2. On the general options page in the “Statement Completion” section override whatever is in the boxes “Auto list members” and “Parameter Information” and makes those checked. Such as shown here:

Statement Completion


That brought back the auto popup for me in VS2013 and should for you as well.  This fix should work with any version of Visual Studio 2008, 2010, 2012 and 2013.

Still having problems? Then see Using Intellisense on MSDN for other troubleshooting suggestions.


It has been reported that ASP.Net users are experiencing a different kind of intellisense failure. If it is web related intellisense look into installing Visual Studio Web tools.  See

Announcing release of ASP.NET and Web Tools 2013.1 for Visual Studio 2012


Fear and Loathing in Visual Studio 2012 at 256 Colors

While working with the Visual Studio 2012 RC I experienced the downside to the new color scheme. When I Citrix-ed into my workstation I adjusted the colors to the 256 color set for better performance over the wire. That was not good.

Now I normally work with the dark color theme and discovered that the appropriately shaded colors simply ran together to the point where text editor window became almost as one the other windows.

Ok, a picture is worth a thousand bug reports, ahem issue reports, so let me show you.

Dark Theme

256 Colors Full Color
256 colors dark True Colors Dark

Light Theme

I decided to switch to the light theme, not that my specific editor colors which work on the dark, do not play well in the light and that has nothing to do with this situation, but notice how in 256 colors the golden rod color becomes prominent in the windows.

256 Colors Full Colors
256 colors Light True Colors Light


How did VS 2010 look in 256 Colors? Just fine thank you!

Ahh nothing ages well like a good editor; Chateau De Studio 2010!

256 VS 2010


Long story short don’t use the non true color setting when remoting in to use Visual Studio 2012!


IIS & Visual Studio 2010: Publishing Gotchas using Web Deploy

On my current project I am in charge of getting a fresh install of Server 2008 R2 with IIS 7.5 running to support a Silverlight web site and its accompanying  WCF service. Here are the some of the error messages and tips and tricks I did to get Visual Studio 2010 Web Deploy to work.

IIS 7.5 Failure Possibilities

Web deployment task failed.(Remote agent (URL http://… //MSDEPLOYAGENTSERVICE) could not be contacted.  Make sure the remote agent service is installed and started on the target computer.)

Remote agent (URL http://… //MSDEPLOYAGENTSERVICE) could not be contacted.  Make sure the remote agent service is installed and started on the target computer.

An unsupported response was received. The response header ‘MSDeploy.Response’ was ” but ‘v1’ was expected.
The remote server returned an error: (503) Server Unavailable.

These errors can come up and for the most part can be fixed on the Server which is running IIS.

  1. Web Deploy package is not installed on the IIS server in question. To install find the “Web Deploy” or “Web Deploy 2.0” from the top level IIS.Net\Download (for downloading all extensions) or directly on the Web Deploy 2.0 page.  Alternately if the Platform installer addin is installed one can find it through the IIS Server Manager where one can also install it and other goodies. (The platform installer as shown below can be found in the Server list or and individual website list of icons in the management section.)
  2. Even if Web Deploy package is installed, the service is not running automatically. Follow these steps to find the correct service and get it running.
    1. Run services.msc from the start bar or command line.
    2. Search for the service named Web Deployment Agent Service. Once found verify it is running and also starts up automatically after a reboot.
  3. Also your account may not have permissions to publish to the web site in question. In IIS Management Studio, find the website in question and make sure your (or other’s) credentials are found in the IIS Manager Permission list.

Fear and Loathing in Visual Studio During Publish

Here are some of the errors one can get when trying to publish

Web deployment task failed.(Could not complete the request to remote agent URL ‘https://{your server name}:8172/msdeploy.axd?site=Default Web Site’.)

Could not complete the request to remote agent URL ‘https://{your server name}:8172/msdeploy.axd?site=Default Web Site’.
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
The remote certificate is invalid according to the validation procedure.

If you get one of the above, it is suggesting that it cannot find your server. To fix this situation, specify the server name with HTTP:// behind it. For example if (on your intranet) you remote to your server named ValHalla Visual Studio expects you to have this in the server line to look like this:
Service URL

No need to have /MsDeploy.axd!

Wait There is More

If you receive any of these errors:

Invalid Service Url

Web deployment task failed. An error occurred when the request was processed on the remote computer.)

An error occurred when the request was processed on the remote computer.
Site ‘OneSource’ does not exist.

Check the website name. Note IIS is setup with at default web site named “Default Web Site”. If that is the case then literally specify “Default Web Site” in the list. Otherwise find the name of the target website and the application/service which has been setup in IIS and make sure one is publishing to that site/name combination. The following example is publishing the OneSource site to a “Default Web Site” in IIS.


I hope this helps (HTH) to any whomever may come after. Smile


Unit Test in Visual Studio Fails to Copy a Critical Configuration File which Fails Test

I ran into this problem when working with Visual Studio 2010. I had a project which had a SQL Server Compact database file (.sdf) which according to the build was to be Copied to the output directory during builds. But the problem was that during my unit testing, this file was not being copied out to the target directory for unit testing and code coverage. Once the test was run, it would fail because the database file could not be found.


To have any ancillary file included in a test output run, one needs to add it to the test deployment.  Here are the steps

  1. In the Solution Items folder of the solution find Local.testsettings file.
  2. Double click the Local.testsettings file
  3. Select the Deployment category.
  4. Choose the file by selecting the Add File button.
  5. Path to the file.

Done and retest to verify.


VS2010: Not Seeing the Obvious – Named Threads in Profile Reports

iStock_000002461629XSmallCall me crazy but I named my kids, I named my pets and heck, yes I even name my threads. Things which are important to me in life are worth naming; right? Thread names for me can be important in debug situations. When one uses the Performance Wizard and chooses to have a Concurrency Visualization profile report, specifically the Threads section the name of a thread is not used.

Historically and in the latest version of Visual Studio 2010 the profile reports ThreadMedo not show the thread names. Why?

Don’t get me wrong on this, Visual Studio Twenty Ten is a great product and light years ahead of all other versions! I look forward to having it share my cube and work computer for eight plus hours a day when it is finally released. But heck a man can dream can he?

Let us take a look at what inspires me to write this diminutive dissertation on a distilled user suggestion…


One can name threads, simply by, well naming it. Here is a code snippet below:

Thread T1 = new Thread(ThreadOne);

T1.Name = "Jabberwocky";


Viola our thread is named. I cannot think of another reason for naming a thread except for debug purposes. Hey did someone mention debug?


Yep while debugging the nice little Threads window as shown above displays our named thread. But yet the Profile Performance reports do not show it. Are the two groups at Microsoft not talking to each other and sharing technology. ;-)

Heck I even tried a trick to Trojan Horse a name into the profiler (Reference the Microsoft.VisualStudio.Profiler dll located in the install directory at  \Team Tools \Performance Tools\)

Thread t = new Thread(new ParameterizedThreadStart(
threadIndex =>

Console.WriteLine("Hello from thread " + (int)threadIndex);

alas to no avail. The report still only shows the type of thread and its generic ID.


I feel that named threads might give one an edge in debugging race or deadlock conditions in code. This is a great tool which frankly could be made even better by including the actual thread names, if found in the report.

Connect Suggestion

If you find this little diatribe interesting go and put your two cents into the Microsoft Connect issue which I created:

Named Threads: Missing the Obvious on Profile Reports

Thanks for your time and well; taking a second look.


Visual Studio 2010 – Fuzzy Text

In loading Visual Studio 2010 beta 1, I was very disappointed. Out of the box, the dialog menu text is fuzzy along with most dialogs. Here is V2010 and Visual Studio 2008 side by side. Notice the File menu text is fuzzy:


Notice toolbox is the biggest offender. Even the colors while editing are not as crisp. Is it just me or do my eyes fail when looking at VS2010? Someone has beat me to writing a Microsoft Connect issue on this one: Fuzzy text display in Visual Studio 2010 Beta 1.