Rectangle 27 11

If you are using a 64-bit machine

Then the problem maybe due to Visual Studio use of 32-bit IIS-Express.

Solution: In Visual Studio, go to Tools menu > Options > Projects and Solutions > Web Projects > Enable the option "Use the 64 bit version of IIS Express" and click ok

Thank you. This fixed the issue on a fresh install of VS2017 on a new x64 Windows 10 machine.

iis express - Process with an ID #### is not running in visual studio ...

visual-studio-2013 iis-express
Rectangle 27 11

If you are using a 64-bit machine

Then the problem maybe due to Visual Studio use of 32-bit IIS-Express.

Solution: In Visual Studio, go to Tools menu > Options > Projects and Solutions > Web Projects > Enable the option "Use the 64 bit version of IIS Express" and click ok

Thank you. This fixed the issue on a fresh install of VS2017 on a new x64 Windows 10 machine.

iis express - Process with an ID #### is not running in visual studio ...

visual-studio-2013 iis-express
Rectangle 27 145

// You can specify all the values or you can default the Build and Revision Numbers 
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: AssemblyVersion("1.0.*")]
//[assembly: AssemblyFileVersion("1.0.0.0")]

you can do this in IDE by going to project -> properties -> assembly information

Assembly File Version: A wildcard ("*") is not allowed in this field

message box if you try place a * in the file version field.

So just open up the assemblyinfo.cs and do it manually.

@greg - yes it should work in vs 2008

It is not desirable to change the AssemblyVersion number during a release cycle. Instead, the AssemblyFileVersion should be changed. See my blog post on this topic: philippetruche.wordpress.com/2008/08/12/ Also see Suzanne Cook's excellent post on when to change the numbers: blogs.msdn.com/b/suzcook/archive/2003/05/29/57148.aspx

I'd be careful using the * it will stop working on June 4th 2179 when the day becomes 65536

c# - Can I automatically increment the file build version when using V...

c# asp.net visual-studio version-control assemblyinfo
Rectangle 27 144

// You can specify all the values or you can default the Build and Revision Numbers 
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: AssemblyVersion("1.0.*")]
//[assembly: AssemblyFileVersion("1.0.0.0")]

you can do this in IDE by going to project -> properties -> assembly information

Assembly File Version: A wildcard ("*") is not allowed in this field

message box if you try place a * in the file version field.

So just open up the assemblyinfo.cs and do it manually.

@greg - yes it should work in vs 2008

It is not desirable to change the AssemblyVersion number during a release cycle. Instead, the AssemblyFileVersion should be changed. See my blog post on this topic: philippetruche.wordpress.com/2008/08/12/ Also see Suzanne Cook's excellent post on when to change the numbers: blogs.msdn.com/b/suzcook/archive/2003/05/29/57148.aspx

I'd be careful using the * it will stop working on June 4th 2179 when the day becomes 65536

c# - Can I automatically increment the file build version when using V...

c# asp.net visual-studio version-control assemblyinfo
Rectangle 27 144

// You can specify all the values or you can default the Build and Revision Numbers 
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: AssemblyVersion("1.0.*")]
//[assembly: AssemblyFileVersion("1.0.0.0")]

you can do this in IDE by going to project -> properties -> assembly information

Assembly File Version: A wildcard ("*") is not allowed in this field

message box if you try place a * in the file version field.

So just open up the assemblyinfo.cs and do it manually.

@greg - yes it should work in vs 2008

It is not desirable to change the AssemblyVersion number during a release cycle. Instead, the AssemblyFileVersion should be changed. See my blog post on this topic: philippetruche.wordpress.com/2008/08/12/ Also see Suzanne Cook's excellent post on when to change the numbers: blogs.msdn.com/b/suzcook/archive/2003/05/29/57148.aspx

I'd be careful using the * it will stop working on June 4th 2179 when the day becomes 65536

c# - Can I automatically increment the file build version when using V...

c# asp.net visual-studio version-control assemblyinfo
Rectangle 27 41

Another way is to use the --debug-brk command line option of mocha and the default Attach launch setting of the Visual Studio Code debugger.

Run mocha from the command line using this command:

mocha --debug-brk

Now in VS Code click on the Debug icon, then select Attach from the option next to the start button. Add breakpoints in VS Code and then click start.

Yes, but it's a bit more than just pressing f5..

I might've found a solution here.

You must add "request": "attach" to the launch.json if it doesn't exist - otherwise it will complain that you must specify a program or some other error.

This seems to be VS Code specific. Doesn't work in normal VS 2015

node.js - Mocha breakpoints using Visual Studio Code - Stack Overflow

node.js tdd mocha bdd visual-studio-code
Rectangle 27 18

If you're using Visual Studio 2010, you can use Ctrl+Shift+Up and Ctrl+Shift+Down to jump between highlighted references and keywords.

Since these are If blocks, the IDE will highlight the Then keyword as well, so just tap Up/Down twice in rapid succession. Up/down wraps, so if you really want to save a keypress, hit the key in the "wrong" direction to get where you want.

Don't know if you could call it "brace matching" but it sure as heck gets the job done! Thanks!

Yeah, that won't help you here. I'm not sure what will help you here.

As I already said, I have no idea. Resharper or similar plugins may have a command, not sure. You should create a new question here for that.

Just a tip: if you were also looking to be able to find the end of a Select statement, it doesn't go from the Select to the End, it goes through each Case, so do a <Ctrl>+<Shift>+<Up> once and it wraps around to the end!

vb.net - Keyboard shortcut for Jumping between "If/End If" - Stack Ove...

vb.net visual-studio visual-studio-2010 keyboard-shortcuts
Rectangle 27 3

If you are using Visual Studio 2010 then I recommend downloading AJAXControlToolkit from Nuget a shown in this post (link).

I yesterday stumbled at the same problem and what worked was changing the prefix to "ajaxToolkit" and doing same thing for script manager as Stephen Walter is showing in this post (link). Please use ToolScriptManager instead of ScriptManager.

<ajaxToolkit:ToolScriptManager id="id12" runat="server"/>

Thanks for the info Mitul. I have tried everything that you suggested. I still don't get <ajaxToolkit> controls in the intellisense. I created a new website, installed AjaxControlToolkit package using NuGet, but the problem remains.

Another way you could try is to do "Add items" to your toolbox window and add .dll that way and then you can drag and drop the controls that way. I think that would resolve the tag prefix.

I have tried that also. I even tried installing AjaxControlToolkit 3.5 instead of 4.0, but that is also not working. Any other idea?

Seems like it has been working all along. I still get the green line under the control definition saying "Unrecognized tag prefix or device filter". But if I go ahead and run the page anyway, it runs ok.

That seems weird. I know you must have done it but have you tried to close and open visual studio. Sometimes my squiggly lines disappear if I do that because vs might correctly reference that way.

c# - Unrecognized tag prefix or device filter (Visual Studio 2010) - S...

c# asp.net visual-studio-2010 ajaxcontroltoolkit
Rectangle 27 1

Manual Creation using the same method Visual Studio uses

If building from scratch and don't care about how Visual Studio does it, you can start with some basics from this solution here, as well as the other links referenced in the accepted solution on the same page.

For reference, some of the files generated by the Visual Studio add reference method below, are stored within a subfolder Web References/Example (where Example is the name of the variable used to access the reference) and contains the following :

<?xml version="1.0" encoding="utf-8"?>
<DiscoveryClientResultsFile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Results>
    <DiscoveryClientResult referenceType="System.Web.Services.Discovery.ContractReference" url="http://example.com/api/index.php?wsdl" filename="index.wsdl" />
  </Results>
</DiscoveryClientResultsFile>

This file is the complete raw wsdl source file (well formatted xml).

This file contains code to initialize all the methods and properties and is the base class which extends System.Web.Services.Protocols.SoapHttpClientProtocol

The properties assigned to the class (sorry I am stripping from an old VB.NET project: look like the following :

<System.CodeDom.Compiler.GeneratedCodeAttribute("System.Web.Services", "4.6.1586.0"),  _
 System.Diagnostics.DebuggerStepThroughAttribute(),  _
 System.ComponentModel.DesignerCategoryAttribute("code"),  _
 System.Web.Services.WebServiceBindingAttribute(Name:="ExampleAPIBinding", [Namespace]:="urn:ExampleAPI"),  _
 System.Xml.Serialization.SoapIncludeAttribute(GetType(MyCustomType1)),  _
 System.Xml.Serialization.SoapIncludeAttribute(GetType(MyCustomType2)),  _

 Partial Public Class ExampleAPI
    Inherits System.Web.Services.Protocols.SoapHttpClientProtocol

 End Class
<?xml version="1.0" encoding="utf-8"?>
<!--
    This file is automatically generated by Visual Studio .Net. It is
    used to store generic object data source configuration information.
    Renaming the file extension or editing the content of this file may
    cause the file to be unrecognizable by the program.
-->
<GenericObjectDataSource DisplayName="MyMethodName" Version="1.0" xmlns="urn:schemas-microsoft-com:xml-msdatasource">
   <TypeInfo>ExampleAPI.SOAP.ClientMerchant, Web References.SOAP.Reference.vb.dll, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null</TypeInfo>
</GenericObjectDataSource>

Right-click your project in Project explorer, and select Add > Service Reference..

If successful (well formatted WSDL is found), the [Add Reference] button will be enabled. Click that, and it will add the reference to your project.

Hehe, that's awesome, mate but I suspect that you missed the disclaimer. I don't have Project Explorer because I'm working with Visual Studio Code (i.e. VS Code not VS 20xx). It's a new, lightweight IDE from MS. Check this out.

@KonradViltersten - I did miss that tag as it's tagged Visual Studio as well. However I am pretty sure you can simply copy the output from that. I don't know if there is a quick way (in either case) to embed a reference as SOAP is quite old (while many still use) I do not believe a natural way was implemented in VSCode.

I fear that you're right. As for the "quite old" part - well, our banking system seems to believe that working with NET 2.0 is okay and NET 3.5 feel too hasty to upgrade to, so I need to work with this dino tech.

@KonradViltersten - I added some sample code from an old VB.NET project which hopefully can assist when building it if doing so from scratch (might be able to do much cleaner than Visual Studio's generated version which imho is rather bloated).

c# - How to reference a WSDL file using Visual Studio Code? - Stack Ov...

c# visual-studio web-services asp.net-core visual-studio-code
Rectangle 27 2

Lots of documentation available. One method for example is to use the Azure management portal UI:

Example:

1. Go to the management portal for Windows Azure (WindowsAzure.com).

2. Create a new web site (see below).

3. Click on the web site to manage and configure it.

4. The manage and configure (dashboard) page is as below.

5. Focus on the quick glance section. Go ahead and create the deployment
   credentials (orange highlight). You will have to provide user name and password.

6. Copy the FTP Hostname and paste it in windows explorer (black
   highlight). In the pop-up window provide the user name and password
   for deployment. Note: the user name has to be given as DOMAIN\USER.        
   The DOMAIN is the web site name that you gave in step 4 above. In my 
   case its TestAzureWS\phani_tpk. (see blue highlight).

7. Folder navigation -> Click on Site, then click on wwwroot.

8. Copy the contents from step 2 above to this folder.

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.

While I agree with you in principle that URL resources change I would add that Microsoft are particular good at referencing old links to the new resource so there is always a path to the relevant information. Thanks for the feedback. Scott.

how to Publish Website (Web Forms) to Azure using visual studio 2010 -...

visual-studio-2010 azure webforms
Rectangle 27 27

I am using Visual Studio 2013 and I have the same issue but it occurs when I try to open a solution that was made using Visual Studio 2010.

The solution for me is to open the solution file (.sln), using notepad and change this line:

[# Visual Studio 2010]
[# Visual Studio 2013]

works like a charm :)

If you have a newer version of Visual Studio, it's usually better to open the file through (this newer version of) Visual Studio (instead of double clicking the .sln file), because it will then perform the necessary conversion (upgrade) to the newer file format (which might be more than just replacing the version number).

But I didn't get what is the Visual Studio Version Selector trying to do. I have never had the Visual Studio 2010 installed (I have 2013 and 2015), so what exactly is it trying to run? Dialog which it opens says "Visual Studio 2010 Shell".

How do I fix an "Invalid license data. Reinstall is required." error i...

visual-studio visual-studio-2010 visual-c#-express-2010
Rectangle 27 78

Also, if you are using Visual Studio 2015 the .vs directory.

@plntxt I'm assuming that currently the packages folder should be part of this list, unless there is some nuance I'm not taking into account.

svn - What Visual Studio files should be ignored by subversion to mini...

visual-studio svn version-control tortoisesvn ignorelist
Rectangle 27 2

Officially VS 2008 is only supported against TFS 2013 (and Visual Studio Online) by using the MSSCCI. However, in practice it still works fine without MSSCCI, MS just no longer tests this particular scenario, so it's not guaranteed to continue working.

Make sure you have the appropriate updates installed, you need:

Order of installation is very important. Refer to this article.

Moreover, if you are still having issues connecting to TFS after successfully installing above mentioned updates, consider clearing your IE browsing history (all checkboxes) and retry.

Just for complementing, after doing all this, you should try to access using full address like this: yourname.visualstudio.com/DefaultCollection

What port should I point to? and should i enable HTTP or HTTPS?

How to connect to visualstudio.com TFS using Visual Studio 2008 - Stac...

visual-studio visual-studio-2008 tfs vsts
Rectangle 27 2

Officially VS 2008 is only supported against TFS 2013 (and Visual Studio Online) by using the MSSCCI. However, in practice it still works fine without MSSCCI, MS just no longer tests this particular scenario, so it's not guaranteed to continue working.

Make sure you have the appropriate updates installed, you need:

Order of installation is very important. Refer to this article.

Moreover, if you are still having issues connecting to TFS after successfully installing above mentioned updates, consider clearing your IE browsing history (all checkboxes) and retry.

Just for complementing, after doing all this, you should try to access using full address like this: yourname.visualstudio.com/DefaultCollection

What port should I point to? and should i enable HTTP or HTTPS?

Sign up for our newsletter and get our top new questions delivered to your inbox (see an example).

How to connect to visualstudio.com TFS using Visual Studio 2008 - Stac...

visual-studio visual-studio-2008 tfs vsts
Rectangle 27 6

For those reading that are using Visual Studio 2008, not Visual Studio 2010 and are getting this error. The answers above did not help me in this situation, so I'm sharing my experience.

If you're debugging an IIS Web application in Visual Studio 2008 by attaching to the w3wp.exe process rather than using the ASP.NET Development Server for debugging (start with debugging), this might be your issue:

Visual Studio might be still referencing a symbol file (file used during debugging) from your dll from an IIS process that is out of date. And that symbol file has been recreated by a .NET source code recompile but the IIS process is still referencing the old symbol file.

Just stop debugging in Visual Studio, restart the web application, and re-attach to the process. Then the breakpoints should turn from yellow (when you see this error) to red again.

Do each bullet in the link below ONE AT A TIME, but repeat my steps below with each one you try.

1.) Stop debugging (press red square icon) in Visual Studio 2.) Clean Solution 3.) Build Solution 4.) [INSERT BULLET INSTRUCTION HERE] 5.) Tools > Attach to Process (or start with debugging) 6.) Start the program that you're attaching to, and run it such that your code will get hit

If attaching to w3wp.exe (IIS site), then open your site in the browser and go to the page that will hit your breakpoint

Today I noticed that if you try debugging on a project that is not set as the start-up project, it will show this. When you attach to your w3wp.exe process, it thinks its debugging on the project that is set as the start-up project. To resolve, just right click the web application project, and choose "Set As Start Up Project". Then try re-attaching to your process.

Good Answer. I just solved it using clean solution. Thanks

Feel free to upvote the answer if it was helpful. :-) I'll show you what upvoting does.

I upvote to your answer as it was helpful. I tried another ways but your's was the one which pulled me out. Thanks +1.

c# - The breakpoint will not currently be hit. No symbols have been lo...

c# asp.net wcf debugging iis
Rectangle 27 5

For those reading that are using Visual Studio 2008, not Visual Studio 2010 and are getting this error. The answers above did not help me in this situation, so I'm sharing my experience.

If you're debugging an IIS Web application in Visual Studio 2008 by attaching to the w3wp.exe process rather than using the ASP.NET Development Server for debugging (start with debugging), this might be your issue:

Visual Studio might be still referencing a symbol file (file used during debugging) from your dll from an IIS process that is out of date. And that symbol file has been recreated by a .NET source code recompile but the IIS process is still referencing the old symbol file.

Just stop debugging in Visual Studio, restart the web application, and re-attach to the process. Then the breakpoints should turn from yellow (when you see this error) to red again.

Do each bullet in the link below ONE AT A TIME, but repeat my steps below with each one you try.

1.) Stop debugging (press red square icon) in Visual Studio 2.) Clean Solution 3.) Build Solution 4.) [INSERT BULLET INSTRUCTION HERE] 5.) Tools > Attach to Process (or start with debugging) 6.) Start the program that you're attaching to, and run it such that your code will get hit

If attaching to w3wp.exe (IIS site), then open your site in the browser and go to the page that will hit your breakpoint

Today I noticed that if you try debugging on a project that is not set as the start-up project, it will show this. When you attach to your w3wp.exe process, it thinks its debugging on the project that is set as the start-up project. To resolve, just right click the web application project, and choose "Set As Start Up Project". Then try re-attaching to your process.

Good Answer. I just solved it using clean solution. Thanks

Feel free to upvote the answer if it was helpful. :-) I'll show you what upvoting does.

I upvote to your answer as it was helpful. I tried another ways but your's was the one which pulled me out. Thanks +1.

c# - The breakpoint will not currently be hit. No symbols have been lo...

c# asp.net wcf debugging iis
Rectangle 27 6

If you're using Visual Studio 2010, you can use the Visual Studio Modeling and Visualization SDK: http://code.msdn.microsoft.com/vsvmsdk

tfs - Get Visual Studio to run a T4 Template on every build - Stack Ov...

visual-studio tfs msbuild t4
Rectangle 27 9

I'm using Visual Studio Professional + Resharper 8.2

I deleted the packages folder and cleared the package cache to fix my issue. Thanks!

No, it doesn't update the .proj files after - so the problem returns -- but good to do it here too :-)

Restoring NuGet packages... To prevent NuGet from restoring packages during build, open the Visual Studio Options dialog, click on the Package Manager node and uncheck 'Allow NuGet to download missing packages during build.'

visual studio 2010 - remove nuget package restore from solution - Stac...

visual-studio-2010 visual-studio msbuild nuget
Rectangle 27 37

If you are using Visual Studio then yes, you can do this.

The library builder tool that comes with Visual Studio allows you to join libraries together on the command line. I don't know of any way to do this in the visual editor though.

lib.exe /OUT:compositelib.lib  lib1.lib lib2.lib

In VS2008, in the project properties of compositelib under Librarian/General, if you check [x] Link Library Dependencies, it will do this for you if lib1 and lib2 are dependencies of compositelib. It seems slightly buggy, I would set the checkbox separately in each build configuration, not once in 'All Configurations'.

VS2015 IDE - don't you use "Additional Dependencies" under Librarian/General to get additional libraries linked directly into the library your project is building?

@davidbak I am trying to figure this out in the last couple of days and apparently this option is obsolete and does not do anything?

c++ - Linking static libraries to other static libraries - Stack Overf...

c++ linker ar .a
Rectangle 27 4

For those reading that are using Visual Studio 2008, not Visual Studio 2010 and are getting this error. The answers above did not help me in this situation, so I'm sharing my experience.

If you're debugging an IIS Web application in Visual Studio 2008 by attaching to the w3wp.exe process rather than using the ASP.NET Development Server for debugging (start with debugging), this might be your issue:

Visual Studio might be still referencing a symbol file (file used during debugging) from your dll from an IIS process that is out of date. And that symbol file has been recreated by a .NET source code recompile but the IIS process is still referencing the old symbol file.

Just stop debugging in Visual Studio, restart the web application, and re-attach to the process. Then the breakpoints should turn from yellow (when you see this error) to red again.

Do each bullet in the link below ONE AT A TIME, but repeat my steps below with each one you try.

1.) Stop debugging (press red square icon) in Visual Studio 2.) Clean Solution 3.) Build Solution 4.) [INSERT BULLET INSTRUCTION HERE] 5.) Tools > Attach to Process (or start with debugging) 6.) Start the program that you're attaching to, and run it such that your code will get hit

If attaching to w3wp.exe (IIS site), then open your site in the browser and go to the page that will hit your breakpoint

Today I noticed that if you try debugging on a project that is not set as the start-up project, it will show this. When you attach to your w3wp.exe process, it thinks its debugging on the project that is set as the start-up project. To resolve, just right click the web application project, and choose "Set As Start Up Project". Then try re-attaching to your process.

Good Answer. I just solved it using clean solution. Thanks

Feel free to upvote the answer if it was helpful. :-) I'll show you what upvoting does.

I upvote to your answer as it was helpful. I tried another ways but your's was the one which pulled me out. Thanks +1.

c# - The breakpoint will not currently be hit. No symbols have been lo...

c# asp.net wcf debugging iis