When you have SP1 installed you&#39;ll see instead:

    Microsoft Visual Studio 2010
    Version 10.0.40219.1 SP1Rel
    Microsoft .NET Framework
    Version 4.0.30319 SP1Rel

Therefore you are still on RTM (release to market) version, not the SP.

RTMRel is the &quot;[release to manufacturing][1]&quot; release. This is when the product is officially launched. If you have SP1 installed, it would say &quot;SP1Rel&quot; after the version (in the case of Visual Studio).


  [1]: http://en.wikipedia.org/wiki/Software_release_life_cycle#RTM

I&#39;m currently writing a class that needs `os`, `stat` and some others.

What&#39;s the best way to import these modules in my class?

I&#39;m thinking about when others will use it, I want the &#39;dependency&#39; modules to be already 
imported when the class is instantiated.


Now I&#39;m importing them in my methods, but maybe there&#39;s a better solution.

Importing modules inside python class

I need to fit two lines in one h1 tag (instead of making two separated h1 tags).

How can I create a line break inside of h1 tag?

Two lines in h1 tag

How can I tell if a computer has Service Pack 1 for Visual Studio 2010 Ultimate?

I assume it is by version number, but I don&#39;t know what version means what. (The version I am looking at is **10.0.30319.1 RTMRel**.)


How can I tell if I have Service Pack 1 for Visual Studio 2010 installed?

How can I tell if a computer has Service Pack 1 for Visual Studio 2010 Ultimate?
I assume it is by version number, but I don't know what version means what. (The version I am looking at is 10.0.30319.1 RTMRel.)

In configuration properties of my project, under the &quot;VC++ directories&quot; there is an entry for &quot;Include Directories&quot;. But under &quot;C/C++&quot; option, there is another entry called &quot;Additional Include Directories&quot;. Same thing happens with library directories.

What are the difference between these two entries?

![enter image description here][1]
![enter image description here][2]


  [1]: http://i.stack.imgur.com/58M2F.png
  [2]: http://i.stack.imgur.com/VH1UA.png
  

What is the difference between &quot;Include Directories&quot; and &quot;Additional Include Directories&quot;

I have a library and a console application that uses a library. The library has a folder with source and header files.

My project is in a child/inner directory but that library directory that I want to include is in a parent/upper directory.

My project directory:

    H:\Gmail_04\gsasl-1.0\lib\libgsaslMain

Includes files are here:

    H:\Gmail_04\gsasl-1.0\src

How can I use paths relative to the project directory, to include folders that are in a parent/upper directory?

How to define relative paths in Visual Studio Project?

Or, should I rather ask, when will VS code formatting work properly for Razor markup? The formatting works for most structures, but it seems to choke on &#39;if&#39; blocks. The code below is as it is formatted by VS. It is very easy to fix this case, with one more indent, but I nicely accepted the formatting in everyday use, and like to use it often for the bulk of my code, so I&#39;d rather avoid manual formatting if possible. Right now I just leave it as VS formats it. 

    @{ 
        if (User.Identity.IsAuthenticated)
        {
        &lt;text&gt;Hello &lt;/text&gt;
        @Html.Display(&quot;@ViewBag.UserName&quot;) &lt;text&gt; - &lt;/text&gt;
        @Html.ActionLink(&quot;Sign Out&quot;, &quot;LogOff&quot;, &quot;Account&quot;, null, new { style = &quot;font-weight: bold;&quot; })
        }
     }

I think it&#39;s important for readability that, e.g. in the above, the body of the if block is indented, besides just looking nicer. 

Why doesn&#39;t Visual Studio code formatting work properly for Razor markup?

If I create a new project in Visual Studio 2010 SP1 and select &quot;WPF Application&quot; and tries to build the generated application, I get the error

&gt; The name &#39;InitializeComponent&#39; does not exist in the current context.

I got a similar error this morning when I tried to build my current project. Yesterday, I had no problem compiling and running it.

I created a new project and got the error whenever I compiled the project. I have just sent the project to a colleague, and he has just compiled without any errors.

What is wrong?


The name &#39;InitializeComponent&#39; does not exist in the current context

Firstly, I apologize for the length of this question. 

I am the author of [IronScheme][1]. Recently I have been working hard on emitting decent debug info, so that I can use the &#39;native&#39; .NET debugger. 

While this has been partly successful, I am running into some teething problems.

The first problem is related to stepping.

Due to Scheme being an expression language, everything tends to be wrapped in parenthesis, unlike the major .NET languages which seems to be statement (or line) based.

The original code (Scheme) looks like:

    (define (baz x)
      (cond
        [(null? x) 
          x]
        [(pair? x) 
          (car x)]
        [else
          (assertion-violation #f &quot;nooo&quot; x)]))

I have on purpose laid out each expression on a newline.

The emitted code transforms to C# (via ILSpy) looks like:

    public static object ::baz(object x)
    {
      if (x == null)
      {
        return x;
      }
      if (x is Cons)
      {
        return Builtins.Car(x);
      }
      return #.ironscheme.exceptions::assertion-violation+(
         RuntimeHelpers.False, &quot;nooo&quot;, Builtins.List(x));
    }

As you can see, pretty simple. 

Note: If the code was transformed into a conditional expression (?:) in C#, the whole thing would just be one debug step, keep that in mind.

Here is IL output with source and line numbers:

      .method public static object  &#39;::baz&#39;(object x) cil managed
      {
        // Code size       56 (0x38)
        .maxstack  6
        .line 15,15 : 1,2 &#39;&#39;
    //000014: 
    //000015: (define (baz x)
        IL_0000:  nop
        .line 17,17 : 6,15 &#39;&#39;
    //000016:   (cond
    //000017:     [(null? x) 
        IL_0001:  ldarg.0
        IL_0002:  brtrue     IL_0009
    
        .line 18,18 : 7,8 &#39;&#39;
    //000018:       x]
        IL_0007:  ldarg.0
        IL_0008:  ret
    
        .line 19,19 : 6,15 &#39;&#39;
    //000019:     [(pair? x) 
        .line 19,19 : 6,15 &#39;&#39;
        IL_0009:  ldarg.0
        IL_000a:  isinst [IronScheme]IronScheme.Runtime.Cons
        IL_000f:  ldnull
        IL_0010:  cgt.un
        IL_0012:  brfalse    IL_0020
    
        IL_0017:  ldarg.0
        .line 20,20 : 7,14 &#39;&#39;
    //000020:       (car x)]
        IL_0018:  tail.
        IL_001a:  call object [IronScheme]IronScheme.Runtime.Builtins::Car(object)
        IL_001f:  ret
    
        IL_0020:  ldsfld object 
             [Microsoft.Scripting]Microsoft.Scripting.RuntimeHelpers::False
        IL_0025:  ldstr      &quot;nooo&quot;
        IL_002a:  ldarg.0
        IL_002b:  call object [IronScheme]IronScheme.Runtime.Builtins::List(object)
        .line 22,22 : 7,40 &#39;&#39;
    //000021:     [else
    //000022:       (assertion-violation #f &quot;nooo&quot; x)]))
        IL_0030:  tail.
        IL_0032:  call object [ironscheme.boot]#::
           &#39;ironscheme.exceptions::assertion-violation+&#39;(object,object,object)
        IL_0037:  ret
      } // end of method &#39;eval-core(033)&#39;::&#39;::baz&#39;

*Note:* To prevent the debugger from simply highlighting the entire method, I make the method entry point just 1 column wide.

As you can see, each expression maps correctly to a line.

Now the problem with stepping (tested on VS2010, but same/similar issue on VS2008):

These are with `IgnoreSymbolStoreSequencePoints` not applied.

1. Call baz with null arg, it works correctly. (null? x) followed by x.
2. Call baz with Cons arg, it works correctly. (null? x) then (pair? x) then (car x).
3. Call baz with other arg, it fails. (null? x) then (pair? x) then (car x) then (assertion-violation ...).

When applying `IgnoreSymbolStoreSequencePoints` (as recommended):

1. Call baz with null arg, it works correctly. (null? x) followed by x.
2. Call baz with Cons arg, it fails. (null? x) then (pair? x).
3. Call baz with other arg, it fails. (null? x) then (pair? x) then (car x) then (assertion-violation ...).

I also find in this mode that some lines (not shown here) are incorrectly highlighted, they are off by 1.

Here are some ideas what could be the causes:

- Tailcalls confuses the debugger
- Overlapping locations (not shown here) confuses the debugger (it does so very well when setting a breakpoint)
- ????

The second, but also serious, issue is the debugger failing to break/hit breakpoints in some cases.

The only place where I can get the debugger to break correctly (and consistantly), is at the method entry point. 

The situation gets a bit better when `IgnoreSymbolStoreSequencePoints` is not applied.


**Conclusion**

It might be that the VS debugger is just plain buggy  :(


**References:**

1. https://stackoverflow.com/questions/4357420/making-a-clr-net-language-debuggable


**Update 1:**

Mdbg does not work for 64-bit assemblies. So that is out. I have no more 32-bit machines to test it on. *Update:* I am sure this is no big problem, does anyone have a fix? *Edit:* Yes, silly me, just start mdbg under the x64 command prompt :)

**Update 2:**

I have created a C# app, and tried to dissect the line info. 

My findings:

- After any `brXXX` instruction you need to have a sequence point (if not valid aka &#39;#line hidden&#39;, emit a `nop`).
- Before any `brXXX` instruction,  emit a &#39;#line hidden&#39; and a `nop`.

Applying this, does not however fix the issues (alone?). 

But adding the following, gives the desired result  :)

- After `ret`, emit a &#39;#line hidden&#39; and a `nop`.

This is using the mode where `IgnoreSymbolStoreSequencePoints` is not applied. When applied, some steps are still skipped :(

Here is the IL output when above has been applied:

      .method public static object  &#39;::baz&#39;(object x) cil managed
      {
        // Code size       63 (0x3f)
        .maxstack  6
        .line 15,15 : 1,2 &#39;&#39;
        IL_0000:  nop
        .line 17,17 : 6,15 &#39;&#39;
        IL_0001:  ldarg.0
        .line 16707566,16707566 : 0,0 &#39;&#39;
        IL_0002:  nop
        IL_0003:  brtrue     IL_000c
    
        .line 16707566,16707566 : 0,0 &#39;&#39;
        IL_0008:  nop
        .line 18,18 : 7,8 &#39;&#39;
        IL_0009:  ldarg.0
        IL_000a:  ret
    
        .line 16707566,16707566 : 0,0 &#39;&#39;
        IL_000b:  nop
        .line 19,19 : 6,15 &#39;&#39;
        .line 19,19 : 6,15 &#39;&#39;
        IL_000c:  ldarg.0
        IL_000d:  isinst     [IronScheme]IronScheme.Runtime.Cons
        IL_0012:  ldnull
        IL_0013:  cgt.un
        .line 16707566,16707566 : 0,0 &#39;&#39;
        IL_0015:  nop
        IL_0016:  brfalse    IL_0026
    
        .line 16707566,16707566 : 0,0 &#39;&#39;
        IL_001b:  nop
        IL_001c:  ldarg.0
        .line 20,20 : 7,14 &#39;&#39;
        IL_001d:  tail.
        IL_001f:  call object [IronScheme]IronScheme.Runtime.Builtins::Car(object)
        IL_0024:  ret
    
        .line 16707566,16707566 : 0,0 &#39;&#39;
        IL_0025:  nop
        IL_0026:  ldsfld object 
          [Microsoft.Scripting]Microsoft.Scripting.RuntimeHelpers::False
        IL_002b:  ldstr      &quot;nooo&quot;
        IL_0030:  ldarg.0
        IL_0031:  call object [IronScheme]IronScheme.Runtime.Builtins::List(object)
        .line 22,22 : 7,40 &#39;&#39;
        IL_0036:  tail.
        IL_0038:  call object [ironscheme.boot]#::
          &#39;ironscheme.exceptions::assertion-violation+&#39;(object,object,object)
        IL_003d:  ret
    
        .line 16707566,16707566 : 0,0 &#39;&#39;
        IL_003e:  nop
      } // end of method &#39;eval-core(033)&#39;::&#39;::baz&#39;

**Update 3:**

Problem with above &#39;semi-fix&#39;. Peverify reports errors on all methods due to the `nop` after `ret`. I dont understand the problem really. How can a `nop` break verification after a `ret`. It is like dead code (except that it is NOT even code) ... Oh well, experimentation continues.

**Update 4:**

Back at home now, removed the &#39;unverifiable&#39; code, running on VS2008 and things are a lot worse. Perhaps running unverifiable code for the sake of proper debugging might be the answer. In &#39;release&#39; mode, all output would still be verifiable.

**Update 5:**

I have now decided my above idea is the only viable option for now. Although the generated code is unverifiable, I have yet to find any `VerificationException`&#39;s. I dont know what the impact will be on the end user with this scenario. 

As a bonus, my second issue has also be solved. :)

Here is a little [screencast][2] of what I ended up with. It hits breakpoints, does proper stepping (in/out/over), etc. All in all, the desired effect.

I, however, am still not accepting this as the way to do it. It feel overly-hacky to me. Having a confirmation on the real issue would be nice.

**Update 6:**

Just had the change to test the code on VS2010, there seems to be some problems:

1. &lt;strike&gt;The first call now does not step correctly. (assertion-violation ...) is hit. Other cases works fine.&lt;/strike&gt; Some old code emitted unnecessary positions. Removed the code, works as expected. :)
2. More seriously, breakpoints fail on the second invocation of the program (using in-memory compilation, dumping assembly to file seems to make breakpoints happy again).

Both these cases work correctly under VS2008. The main difference is that under VS2010, the entire application is compiled for .NET 4 and under VS2008, compiles to .NET 2. Both running 64-bit.

**Update 7:**

Like mentioned, I got mdbg running under 64-bit. Unfortunately, it also have the breakpoint issue where it fails to break if I rerun the program (this implies it gets recompiled, so not using the same assembly, but still using the same source).

**Update 8:**

I have [filed a bug][3] at the MS Connect site regarding the breakpoint issue. 

Update: Fixed

**Update 9:**

After some long thinking, the only way to make the debugger happy seems to be doing SSA, so every step can be isolated and sequential. I am yet to prove this notion though. But it seems logical. Obviously, cleaning up temps from SSA will break debugging, but that is easy to toggle, and leaving them does not have much overhead.


  [1]: http://ironscheme.codeplex.com/
  [2]: http://www.screencast.com/t/Tjrkjl7By
  [3]: https://connect.microsoft.com/VisualStudio/feedback/details/684089/
  [4]: https://connect.microsoft.com/VisualStudio/feedback/details/551765

Making your .NET language step correctly in the debugger

Scenario:

I set up successfully TFS2010 webdeploy task for solution. Everything worked fine until suddendly something went wrong in the deployment task.

Solution has 2 web projects..those are configured to deploy on build and publish it to the dev-server.

Does anybody have a knowledge what is wrong in build (information below)?

    C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets
    (3847): Web deployment task failed.
    ((4.8.2011 11:01:10) An error occurred when the request was processed on the remote computer.)
    (4.8.2011 11:01:10) An error occurred when the request was processed on the remote computer. Unable to perform the operation. Please contact your server administrator to check authorization and delegation settings.

I can give more information if someone needs it.

Content Type	Original Author	Original Content on Stackoverflow
Question	Vaccano	View Question on Stackoverflow
Solution 1 - Visual Studio	Kate Gregory	View Answer on Stackoverflow
Solution 2 - Visual Studio	Nathanial Woolls	View Answer on Stackoverflow

How can I tell if I have Service Pack 1 for Visual Studio 2010 installed?

Visual Studio Problem Overview

Visual Studio Solutions

Solution 1 - Visual Studio

Solution 2 - Visual Studio

Two lines in h1 tag

Importing modules inside python class

Attributions