Sometimes, when I press F1 in Visual Studio Code Editor, it opens browser with MSDN page for .NET Micro Framework. My projects are using .NET Framework 4.5 and there is no trace of Micro Framework in them.
For example pressing F1 over MulticastDelegate in my code editor opens this link instead of this link.
Anybody has the same issues?
UPDATE:
As Jeff Braaten suggested, I checked Debug help context and it seems fine. There is no difference (except the keyword) between context for Action and MulticastDelegate, for example.
And the same tells generated URL
For Action:
http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1
&l=EN-US&k=k(System.Action);
k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);
k(DevLang-csharp)&rd=true
For MulticastDelegate:
http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1
&l=EN-US&k=k(System.MulticastDelegate);
k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);
k(DevLang-csharp)&rd=true
So, most likely, it's not how VS generates request, it's how MSDN search engine interprets it.
This is a known issue with F1 and Visual Studio 2012. We are working on it, and there is no workaround at this time. For now, you'll need to use search to find the correct topic. Robin Reynolds-Haertle, Documentation Manager
It seems that Visual Studio is incorrectly building the Version key-value pair with a = instead of -, which then gets converted to %3D when the address is URL encoded.
If you replace the %3D in this section of the URL
k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.5);
with a -, you get the correct .NET Framework 4.5 MSDN page.
So, the correct address for MulticastDelegate would be:
http://msdn.microsoft.com/query/dev11.query?appId=Dev11IDEF1
&l=EN-US&k=k(System.MulticastDelegate);
k(TargetFrameworkMoniker-.NETFramework,Version-v4.5);
k(DevLang-csharp)&rd=true
I know this has been a long-standing issue with F1 and Visual Studio, but this has been finally fixed. So now, when you press F1 in Visual Studio, MSDN should open the right topic for you.
Related
It looks like Visual Studio 2017 switched its online reference documentation from .Net Framework to .Net Core: every time I hit the F1 key, I get sent on .Net Core documentation for the type/method on which the caret was.
Very well if I were in a .Net .Core project, but it does it too on .Net Framework 4.6.1 projects. And on this .Net Core help, there is no Show other versions drop down list. (Which is understandable, that is not really a newer version of .Net Framework 4.x.)
This renders this key almost useless to me. I end up googling the type / method for getting the MSDN .Net Framework 4.x documentation. (Which is currently more complete for subjects existing in both, compare this and this.)
Is there any way to get the F1 key to open from Visual Studio 2017 the .Net Framework 4.x documentation for the type/method on which the caret is?
I have found no settings for that neither in Help nor in Tools/Options.
This issue affects only online help. Technically Visual Studio does not seem to be blamed. It launches the browser on a MSDN website url with parameters specifying the framework and its version. But MSDN redirects regardless to .Net Core documentation. So it now appears to me as a MSDN website bug.
Example url on which Visual Studio 2017 sends:
http://msdn.microsoft.com/query/dev15.query?appId=Dev15IDEF1&l=EN-US&k=k(System.Runtime.Serialization.StreamingContext);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.6.1);k(DevLang-csharp)&rd=true
Resulting MSDN redirection: 301 => https://msdn... then 302 =>
https://learn.microsoft.com/en-us/dotnet/core/api/system.runtime.serialization.streamingcontext
While Visual Studio 2015 sends on:
http://msdn.microsoft.com/query/dev14.query?appId=Dev14IDEF1&l=EN-US&k=k(System.Runtime.Serialization.SerializationInfo);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.6.1);k(DevLang-csharp)&rd=true
Which only redirects to the https version of the url, then serves the page.
Now this has changed.
As already stated in my question edit, that is more a documentation web site trouble than a Visual Studio trouble.
Moreover, the learn.microsoft.com web site has now changed its redirection. For the provided example, it now gets redirected to (no more core in the path):
https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.streamingcontext
Which redirects further to:
https://learn.microsoft.com/en-us/dotnet/api/system.runtime.serialization.streamingcontext?view=netframework-4.7
Well, still not the asked framework (4.7 instead of 4.6.1), but way better than landing on .Net Core documentation instead of .Net Framework.
It also looks as complete as msdn documentation, though not giving the option to see documentation for versions prior to 4.5.
And indeed in my few tests, changing the version does not seem to reload the page, it seems a bit cosmetic for now... In fact, that is the Core reference documentation which is now gone!
So that move from msdn to docs looks like a bit premature, the learn.microsoft.com site seems to be still a "work in progress" site.
Anyway, it does not look to me there is anything to do on Visual Studio 2017 side. Just wait for the new documentation site to get finished.
I have got Visual Studio 2010 installed on my computer.
Hitting F1 while the cursor is on a .Net element - a class name for instance - does not launch the corresponding MSDN page in my web browser.
Hitting F1 works for some of my workmates at my company.
What option do I need to configure to get it working ?
Within Visual Studio, choose Help-Manage help settings. At that point, you can setup the MSDN Library to use the online reference.
Once this is done, F1 should trigger the proper MSDN page.
I am using Sandcastle Help file builder (1.9.4.0), Sandcastle (2.7.0.0) and .NET Framework 4.0 assemblies to generate the Class reference for Visual Studio.
I have used Framework version is .NET 4.0.30319 and Help File Format is MSHelpViewer and Presentation Style is vs2005 in Sandcastle Help file builder. It is working fine in VS 2010 (Help viewer 1.1). It shows Script error in VS 2012 (Help Viewer 2.0).
Shall I need to change any settings to solve this issue?
I randomly get this error. There's a lot of stuff online that requires you to mess with the registry and such. A much easier solution I found somewhere is to go to select Manage Content icon, and then make some change to the Help contents that you have selected, for example Add in some help topic that is currently not in, or Remove some topic. Then click Update, and its usually fine after that!
In Visual Studio 2010, is it possible to display a start/welcome page when opening a solution file?
I'd like to have some way to show build information to new developers joining the team.
Have you already considered writing your own extension for Visual Studio?
Soma Somasegar has pointed out where to start in his blog here.
You will need to install the Visual Studio SDK (online documentation here) from samples at MSDN.
I have not done this myself yet, but I know that you can create tool windows that already load with Visual Studio. You can request a notification when a solution is loaded and then execute your own custom code.
(I just read about the notfications yesterday in Rico Mariani's blog).
Should be possible. :-)
I’m using visual studio 2008 and moles version 0.93. Everything works well except when I try to debug any test that uses a Moled type. The test skips all my breakpoints. And I get the following message in the output window:
Unable to attach. Check for one of the following.
The application you are trying to debug uses a version of the Microsoft .NET Framework that is not supported by the debugger.
The debugger has made an incorrect assumption about the Microsoft .NET Framework version your application is going to use.
The Microsoft .NET Framework version specified by you for debugging is incorrect
Please see the Visual Studio .NET debugger documentation for correctly specifying the Microsoft .NET Framework version your application is going to use for debugging.
If I try debbuger.Break () I get a message: "No symbols are loaded for any call stack frame. The source code cannot be displayed."
I’m in a crunch right now chasing an issue with one our main components and it has been a pain (like I need novocaine) trying to figure anything out without being able to step through the code.
I want to take advantage of mole's "smooth debugging experience". However, I can't seem to get the debugger to attach at all.
Thanks,
Bzz
See the solution to this issue here:
http://social.msdn.microsoft.com/Forums/en/pex/thread/91c08bf4-3260-458c-a221-91f030a75499
I had this problem when I moved a project from Visual Studio 2010 to Visual Studio 2008. Here's what I did to fix it.
Close Visual Studio. Navigate to the Debug/bin location. Delete the following files:
*.vshost.exe
*.vshost.exe.config
*.vshost.exe.manifest
Open the solution. Goto the project Settings. Under the Application Target Framework, select a framework lower than the one you are working with (you'll set it back later). Visual Studio will close and re-open your project automatically. Then set the Target Framework back to the original version you were working with. Rebuild all, and debugging will work properly.