Docker support is not enables in visual studio 2022 - visual-studio

I created a sample Asp.net web api project to deploy in docker and access it.I haven't made any code changes just create a project and run.it is running in visual studio but when i copy published files to IIS server in local machine and try to access the url it is throwing 404 error.Could anyone please help to resolve this.

Related

Login into my deployed Umbraco back office is causing "An error has occurred.". How do I find out what is wrong?

I have deployed my Umbraco installation by using Visual Studio and the regarding nuget package version 7.4.1 and I am using Azure DB as a back-end. When I try to login I get the following message:
The logs in the folder "/site/wwwroot/App_Data/Logs/" do not show anything. Using http or https does not make any difference.
When I start Umbraco from within Visual Studio (connected to my Azure DB back-end) in debug mode the login works perfectly:
How can I find out what the issue is?
Connecting to the backend with Open Live Writer helped me to unveil a detailed error message. By mistake I have deleted one of the caching folders (App_Data\TEMP\PluginCache).

How to Publish an Umbraco Intranet?

I have just completed an Umbraco intranet using WebMatrix. Now I want to publish it to our server so that everybody can see and use it. WebMatrix can only do Web Deploy or FTP, so I opened the project in Visual Studio 2013 to publish it there. I was able to publish it to my desktop, where I have attempted to get it running here before uploading to the server. So in IIS I 'Add a Website' and set up the project, using port 101. I tried it both on my desktop and then moved it to wwwroot and in both cases IE says 'This page can't be displayed'. I am using the CE database with Umbraco 7.2.4.
Help please. I've been at this for days now.... I've tried the umbraco forum and google and got nowhere. :(
Tony
If you have remote desktop access to your web server, you don't actually need to rely on web publishing. You can just build the website in release mode, and then copy all the folders from the web project onto the webserver.
On the web server you can manually set up an IIS website and set up host names etc. You shouldn't need to deploy it using visual studio, this way is much safer
In IIS, you should set up a new website, using port 80 on your HTTP binding.
From the sounds of the error, IIS is not looking at the right physical path.
You should use the Microsoft guide on How to set up your first IIS Web Site as a starting point.

Invalid Host Name when access app in sharepoint 2013

I'm new to sharepoint and start to learning develope in sharepoint.
When I start deploy an app to sharepoint a local server, it deploy successful with no error.
But when I access to the app, it's always bad request: invalid host name.
I have followed many instruction to config app in sharepoint but problem is not solved.
Can anyone help me to fix it?
I'm using Visual Studio 2013 and Windows Server 2012 to host SharePoint 2013
Thanks
After deploying App for SharePoint your hosts file is going to be updated with appropriate records like below.
127.0.0.1 app-93b7514a6939cb.apps.3p18 # 78f68cdc-80f8-4a75-8cc2-aa82985bc6a1;http://3p18:2121/
::1 app-93b7514a6939cb.apps.3p18 # 78f68cdc-80f8-4a75-8cc2-aa82985bc6a1;http://3p18:2121/

Visual Studio 2010 published web site returns "Could not load assembly App_Web_xxxxxx.dll"

I am working on client's application in which we have two servers - development server and testing server. We first develop applications on development server and then publish it and host it on test server for client testing.
Testing server has Microsoft .NET framework 3.5 SP1. On development we have Visual Studio 2010.
We publish the website on development server using VS 2010 and then copy that folder to testing server and host it on its IIS.
Whenever we try access any aspx page of site hosted on testing server, we get error:
Could not load assembly App_Web_xxxxxx.dll". Make sure it is compiled before accessing the page
What can I do to resolve this?
This could be due to a lot of reasons.
I would start by trying one of the following things..
Make sure your IIS Site has the correct .net version specified - same as your application
Make sure you have all the required .net components installed in windows features (control panetl)
Look at event viewer for more errors and post it here
OK guys here is the solution.
Since my testing server is having Microsoft .NET framework 3.5 so on the development server while publishing from VS 2010, I have to choose target framework as 3.5.
Do this:
Right click web site -> Property Page -> Build -> Change the target framework.
After doing this setting, publish the web site again.

I want to keep my source protected on my development machine, how would I deploy ASP.NET MVC to the server?

I'm not exactly sure what to do, normally I do a commit to SVN and Cruise Control does all this stuff on the server to pull from the repo and deploy everything.
However I am just playing around for fun with my personal VPS and want to know how I can from Visual Studio 2010 (web express) on my local machine just make some kind of installer or DLL or whatever and how to deploy it to my VPS of Windows Server 2008.
Do I upload via FTP and run something or place some files in a certain location and configure through IIS? Or is there some way Visual Studio can just interface with my server and impregnate it with my beautiful code?
From the description given, I'd recommend 2 options:
check whether your server installation currently supports one-click publishing. It's likely an IIS configuration task(s) and/or ensuring your server supports MSDeploy/WebDeploy. See "One-Click Publishing - What's New". Publish Use Visual Studio 2010's Publish command to perform a Web Deploy of your solution.
setup an FTP server on your server. Use Visual Studio 2010's Publish command with the FTP option to push your built solution.
Would this MSDN article help?
The thing is there's capabilities in Visual studio that can publish a web application on a web server.
But you can always do an xcopy deployment as well. And since you've obviously never deployed a web application yet maybe it would be good to learn something and actually deploy it manually.

Resources