I have installed BizTalk 2013 R2 on Windows Server 2012 R2 and Visual Studio 2013 Ultimate is also installed on the same machine.
I cannot see BizTalk Project template while creating a new project in Visual Studio.
When I ran the BizTalk setup again, Developer Tools box was not selected. When I select the box it gives following message
Features you selected requires the following components to be installed:
WCF HTTP ACTIVATION 4.5, IIS ASP NET 4.5
When I check in the Server Manager, both of the above are already installed.
Kindly help me resolve this issue.
Have you registered ASP.NET 4.5 on the machine?
Try running this command:
aspnet_regiis -i
You can read more about the ASP.NET IIS Registration Tool (Aspnet_regiis.exe) here:
http://msdn.microsoft.com/en-us/library/k6h9cz8h%28v=vs.100%29.aspx
The easiest way to do this would be to run the Visual Studio Command Prompt.
Also make sure to run as an administrator.
To restore the default project templates
In the command prompt, navigate to the location of devenv.exe. This file is located in \Common7\IDE.
Type "devenv /installvstemplates" and press Enter.
NoteNote:
If you are using an Express Edition of Visual Studio, type "Express /installvstemplates" where is either VB, VJS, or VCS for Visual Basic, Visual J#, and Visual C#, respectively.
If this procedure does not restore the default templates, reinstall Visual Studio.
U can follow this link also:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/f1cd2e14-1d7e-4b84-8bc2-871d67e2a942/devenvexe-installvstemplates-not-install-propertly
Related
I did full install of BizTalk including developer tools (after installing Visual Studio 2019). I have also done a repair and reboot since then.
I see this .vsdir file on the disk: "c:\Program Files (x86)\Microsoft BizTalk Server\Developer Tools\BizTalkProjects\BTSProjects.vsdir", but not sure how to make it work with VS2019.
File contains this:
Schema Files|{7a51b143-7eea-450d-baef-827253c52e43}|#221|140
BTSFlatFileSchema.vsz|{7a51b143-7eea-450d-baef-827253c52e43}|#134|7|#135|0|229|0|#136
JSONSchemaWizard.vsz|{7a51b143-7eea-450d-baef-827253c52e43}|#144|8|#145|0|229|0|#146
##Documentation about Adding Wizards to the Add Item could be found here http://msdn.microsoft.com/en-us/library/2sc7ft4a.aspx
The link in the file refers to a Visual Studio 2014 web page.
Expected result, click "Create New Project" in BizTalk, type BizTalk and be able to pick the template.
I have tried these two commands that might have fixed in older releases, not sure if they are applicable with VS2019:
devenv /setup templates
devenv /InstallVSTemplates
Copied from Biztalk 2020 - Project not showing in Visual Studio 2019
From the installer:
".To use this feature, you must also install the following: BizTalk Project Extension, Enterprise Single Sign-On (SSO) Administration.For more information on this component, click Help. "
And the Install BizTalk Server 2020 documentation:
To complete Developer Tools component installation, install BizTalk Server extension in Visual Studio.
To achieve this you need to:
Start Visual Studio and load into an empty IDE
Click Extensions, Manage Extensions
Search the online tab for BizTalk Server:
Install the BizTalk Server extension
Close all instances of Visual Studio
Let VSIX installer complete
Start Visual Studio and select BizTalk from the project types
We have an ASP.NET web application already deployed to Azure. I'm trying to create a new development virtual machine (using VirtualBox). Everything seems to work fine. I can run the project locally, but when I click on Publish, I just get a comment in the Output window: "The build has been canceled".
The same project using the same version of Visual Studio 2015 Update 1 can be deployed without any problem from the other development PCs (they are NOT virtual machines, don't know if it matter or not).
I use the latest version of all extensions installed. I have 'repaired' my Visual Studio Installation, just in case.
Any suggestions?
Note : I just tried to publish a new, empty ASP.NET 5 Web Application. I got the same "The build has been canceled" message.
The problem seems to be VirtualBox (or Visual Studio 2015 in VirtualBox). I can't publish any website from any VirtualBox VM but I can publish all of them from the PC where the VM is running.
I have downloaded this blog engine
https://github.com/lelandrichardson/MiniBlog
I cannot run it within Visual Studio because it wants IIS : how to change this ?
If your project doesn't load in Visual Studio (it is greyed out), you need to manually edit the project file (MiniBlog.csproj) in a text editor. You just need to look for the UseIIS tag, and change its value to False:
<UseIIS>False</UseIIS>
When you do the above, Visual Studio should be able to load the project. It should now default to the Visual Studio web server.
Once you are able to load the project in Visual Studio, you can choose another web server, if you wish. You just need to right-click on the project in the tree view and then select Properties. From there, if you open the Web tab, you can choose the legacy Visual Studio Web Development Server, IIS Express (you may need to install this), or the Server version of IIS.
Just a note - I was unable to actually build the project that you linked to. There appear to be missing dlls, but that is out of the scope of this question.
try to add IIS Express 7.5 for visual studio http://www.microsoft.com/en-us/download/details.aspx?id=1038
when i am trying to attach a process(w3wp.exe) in asp.net (visual studio 2008), i couldn't attach it , it displays the following error
i have repaired the visual studio 2008, after seen this. again i got the same error as shown above when i am trying to attach a new one.
why this happens, is i need to download any other service pack or visual studio 2008 remote debugger installation ( as mentioned in the error box),. please help me to fix it.
According to here, there should be a remote debugger setup file on the VS2008 disc in a folder called "Remote Debugger\x64" or "WCU\RDBG\x64".
You could also try downloading and installing the Visual Studio 2008 Service Pack 1 Remote Debugger.
I have a requirement to work on a VS2003 web project.
I have VS2008,vs2010,vs2003 installed in my system
Other System details are
Windows Xp professional version 2 service pack 3. IIS 5.1
When i am trying to create a VS 2003 web project giving the localhost as path
i am getting the following error.
visual studio noted that specified web server is not running under asp .net 1.1 version.You will be unable to run asp .net web applications or services
I have used aspnet_regiis commands as well as a tool(ASPNETVersionSwitcher.exe ) to swith versions and in IIS also default web site ASP.NET version chosen as ASP.NET 1.14322.
I am still getting the error.
same error I get ,if I point a virtual directory in the existing 1.1 .NET web application and trying to open it.
Please advise, I have to work on this project as soon as possible.
Make sure all IIS Applications are using the same version of the framework. It is possible to have both 1.x and 2. I typically, uninstall using aspnet_regiis /ua which uninstalls all ASP.NET versions, then use aspnet_regiis to install ASP.NET as needed.
Make sure the "Virutual Directory" ASP.NET properties are correct for the version of Visual Studio you are using. Obviously, you cannnot use VS2k3 to connect to a ASP.NET 2.0 Virtual Directory.
Following is a dump of my installed ASP.NET versions.
C:\Program Files\Microsoft Visual Studio 9.0\VC>aspnet_regiis -lv
1.1.4322.0 Valid (Root) C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\asp
net_isapi.dll
2.0.50727.0 Valid C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\as
pnet_isapi.dll
4.0.30319.0 Valid C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\as
pnet_isapi.dll
C:\Program Files\Microsoft Visual Studio 9.0\VC>aspnet_regiis -lk
W3SVC/ 1.1.4322.2443
W3SVC/1/ROOT/ 2.0.50727.0
W3SVC/1/ROOT/Reports/ 2.0.50727.0
W3SVC/1/ROOT/ReportServer/ 2.0.50727.0
W3SVC/1/ROOT/ExceptionService/ 2.0.50727.0
W3SVC/1/ROOT/verification/ 2.0.50727.0
I've seen people create a virtual machine (pc) using Windows XP as the guest OS. They would then install Visual Studio 2003 on the virtual machine and do their development there.
From what I gather those people ran into a similar issue like yours.
Another solution that I have heard was that Visual Studio 2003 needs to be installed first, before Visual Studio 2005, 2008, or 2010 are installed. I've heard that works, but only from a clean OS install (you can't uninstall all the versions and start over.)