Understanding VS2022

Joined
Apr 29, 2023
Messages
17
Reaction score
1
I am not a VB/.NET programmer. Long ago a friend wrote a website for me. I managed to support it with VS2010 on my PC and the GoDaddy hosting site. I decided to move to Win11 Pro. Installed VS2022 Community. Finally got SQL Server 2022 Development working. Made a change to a page. Used Web Deploy to publish to local IIS. If I use http://localhost/mysite in a browser it works. But there is no folder under C:\inetpub\wwwroot\mysite

Where is my published site and why there? Why not in wwwroot? How do I fix it? Is it safe to use FTP to publish to GoDaddy like I did with VS2010? I don’t want to screw up my ‘production’ site.
 
Joined
Mar 31, 2023
Messages
95
Reaction score
8
It sounds like you may have published your site to a different location than the default wwwroot folder. By default, when you use Web Deploy to publish a site to a local IIS instance, it should publish to the wwwroot folder. However, it's possible to change the publish location during the publish process.

To find out where your site was published, you can check the publish settings in Visual Studio. Open your project in Visual Studio, right-click on the project in the Solution Explorer, and select "Publish". In the "Publish" dialog box, select the publish profile that you used to publish your site. Then, click the "Edit" button next to the profile.

In the "Connection" tab of the publish profile settings, you should see a "Destination URL" field that specifies the destination server and site. The "Site/application" field should specify the virtual directory where your site was published. You can click the "Test Connection" button to ensure that you can connect to the destination server.

Once you've found the location where your site was published, you can check the IIS settings to ensure that the virtual directory is configured correctly. Open the IIS Manager and navigate to the site where your virtual directory is located. Expand the site and find the virtual directory. Right-click on the virtual directory and select "Manage Virtual Directory" -> "Advanced Settings". In the "Physical Path" field, you should see the path to the folder where your site was published.

If the physical path is not correct, you can change it to the correct path. Once you've made the changes, you may need to restart the website or the application pool to ensure that the changes take effect.

As for publishing to GoDaddy, you should be able to use FTP to publish your site just like you did with VS2010. However, make sure that you use the correct credentials and settings for your GoDaddy account. You may want to test your FTP connection first before publishing to ensure that you can connect to the correct server and directory. Also, make sure that you have a backup of your production site before making any changes.
 
Joined
Apr 29, 2023
Messages
17
Reaction score
1
Many thanks. Some of the references to options were not exact but I figured it out. When I started up I never specified locations for the site. The attached shows the connection option. I have changed them to be what they need to be.


pub1.jpg
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,767
Messages
2,569,571
Members
45,045
Latest member
DRCM

Latest Threads

Top