Here is My current versionTrying to create my first website using Visual Studio 2010. I configured IIS, installed ASP.NET MVC4 (not sure if I need it though). But still unable to see anything when clicking Visual Basic or VisualC#. What am I missing?
Related
I have developed ASP.NET project in Visual Studio 2019. When I try to run the project with IIS Express, the webpage says “This site can't be reached” and "The connection was reset".
In taskbar I can see that IIS Express is working and I'm able to debug and step though my code till the very end successfully so I know the service is executing fine without any errors.
Site can`t be reached
I created a new project, just to ensure that there weren't any errors within my config or build files. When I run the new project, I get the same result.
I tried with other browsers as well, but still the same error.
I repaired the Visual Studio using the Visual Studio Installer, and reset everything to default, and had no success with that.
I tried to delete hidden vs. folder and had no success.
Any advice on how to resolve this would be greatly appreciated.
Thanks!
I fixed the issue by deleting Kaspersky Antivirus.
In my solution, I have two projects: an WPF application and an ASP.NET Web API 2 created using the defaults. Under the API Properties - Web tab, I'm using IIS Express.
On the Solution Property Pages, I have Single startup project checked, with the WPF project selected. I can confirm this is the startup project because the WPF application is bolded in Solution Explorer. I've verified none of the IIS Express sites are running in the task tray.
When I hit F5, both the WPF and the Web API start running.
Is there a setting I'm missing somewhere? Why is the Web API starting despite not being the startup project?
In Visual Studio 2017, navigate to View > Properties Window. Then click the Web API project name in Solution Explorer, and set the Properties window's Always Start When Debugging option to False.
So, we have a web app we've migrated to .net core, and while it runs fine in Visual Studio 2017, because Visual Studio uses its "launchSettings.json" file to configure how IIS Express will work/launch - I, for the life of me, cannot figure out how to get VS Code to run the project. The problem is, we use HTTPS only and have always just let IIS Express used the self-signed locahost cert to allow this, so when debugging the site locally, we'd always use https://localhost:44300. As stated, this worked fine when entering this url in the launchSerttings.json file for Visual Studio, but VS Code does not use this, and the only answers I can find on this always refer to having to use the Kestrel Server's .Listen() method and used a self-signed cert and password to allow the use of an HTTPS port. 1) this seems just silly that I'd have to add this "test" code to run it locally, because I don't need it when we deploy to Azure, as Azure manages the certs and url for us. 2) Visual Studio 2017 does not need any specification on Kestrel to make this all work. So, I have hard time believing there isn't some extension, or process to achieve the same thing in Visual Studio Code that Visual Studio is doing under the hood to allow IIS Express to communicate with the .Net Core Kestrel Server.
Combing through the all the documentation suggests that the ASPNetCoreModule is what handles this communication for IIS and Kestrel, so, I would hope/guess there has to be some way to configure the web.config file's tag to include something that would make this work.
I've previously used and tried other IIS execution extensions in VS Code, but those focus on elements in the project's web.config to boot IIS which are no longer present in the web.config due to it being a .Net Core app. I had been successfully running the web app with the IIS Express Executor extension before migrating to .Net Core when the web app was a .NET Framework 4.5.2 app
So, the end goal is that I need to be able to go to https://localhost:44300 in the browser, and have our site work, but I don't want to have to add any sort of test-cert into the Kestrel config in the Program.cs or Startup.cs files. If there's no way to do this, then that will be really disappointing considering Visual Studio makes this seem like it should be very simple.
Thanks for the help.
Was able to get this to work using the following steps.
1) Install IIS Express executer in VS Code or any other similiar extension that wraps around dotnet commands
2) Download Process Explorer from https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer
3) Launch Visual Studio IIS Express as you would normally
4) Open Process Explorer (may need to launch as Admin) and locate iisexpress.exe -> VSIISExeLauncher.exe
5) Right click VSIISExeLauncher.exe and click properties then locate the "Environment" tab. Inside the environment tab you will see 2 variables: LAUNCHER_PATH and LAUNCHER_ARGS. Copy both of these variables and values.
6) Next locate the configuration file for the extension you installed in VS code (mine is launch.json inside the .vscode folder in your project root directory). It will likely have an "environment" or "env" section for adding environment variables to the launch arguments. Add the two arguments copied from step 5. These vary from person to person so the value of the arguments will be unique to your machine.
7) Launch IIS-Express from vs code. My particular command for this is "IIS-EE: Start IIS Express Server" but will vary based on the extension you installed. You can hit F1 to launch commands.
Visual Studio itself uses too many tricks under the hood to make you believe it is simple. However, it is not.
I documented all necessary details in a blog post,
https://blog.lextudio.com/how-visual-studio-launches-iis-express-to-debug-asp-net-core-apps-d7fd3677e3c3
And if you follow the steps manually, you should be able to launch IIS Express the same way VS does, and then use that in Visual Studio Code. I know there is some VSCode extensions trying to integrate with IIS and IIS Express, but I do hope those authors spend more time learning such integration and improve their extensions to fully support the scenarios.
I'm trying to get a SharePoint 2010 web portal working for a TFS 2012 team project. Most of the functionality is working, but I'm having a difficult time getting the custom work item controls we've built working in the SharePoint Project Portal site. (They're working fine within Visual Studio, we haven't tried getting them working in the default TFS Web Access portal.)
My questions are:
Since the TFS Web Access method for creating custom properties have been updated, is that method appropriate for the SharePoint site? (I doubt it, since jQuery is necessary and isn't included by default in SP 2010, but I thought I'd ask.)
Whenever I try to test this, all I get is "Error: Unable to create 'FieldName'" with nothing in the ULS logs. Is there any way I can debug this?
Are there any examples available online that I may have missed in my searches?
After a lot of digging and frustration, I have finally gotten a simple control working. Indeed, SharePoint 2010 expects the custom controls to be formatted similarly to Web Access 2010, not Web Access 2012. Here is an example that helped:
http://code.msdn.microsoft.com/windowsdesktop/CSTFSWebAccessWorkItemMulti-ace1b01e
Also, if you install the 2008 Team System Web Access (yes, 2008), you'll get a Word document with some helpful documentation.
Here are some caveats:
The Word documentation states that the control needs to inherit from both IWorkItemControl and IWorkItemWebControl. Since IWorkItemWebControl contains all of the fields that IWorkItemControl does, and IWorkItemControl is declared in a DLL that references .NET 4.5 (not good for SharePoint 2010), I referenced only IWorkItemWebControl and it seems to work.
The documentation states that your control needs to inherit from System.Web.UI.Control to work, but the UserControl doesn't work. I had to inherit from one of the WebControls to get it to work.
The custom controls need references to TFS 2012 versions of several DLLs (which are listed in the sample download), but the only place I found them were in the GAC on the SharePoint server. So I copied them from the GAC onto my local machine for development.
Deploying is easy - all you need to do is place the .wicc file and the DLL into "Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\Tswa\CustomControls".
If I find anything else, I'll post it here.
Is it possible to have a visual studio solution arranged such that there is a:
x.sln
x.Web.csproj -pure html/js/css
x.MVC.csproj -routes and standard webapi
Where the MVC site runs and hosts the web project i.e. out of the Views/Static. on the same server. Perhaps as a virtual directory? That way they can be developed and tested separately but deployed and with the option to run them together.