Everything was working just fine and on the last publish my wordpress directory is now gone.
I don't have a folder with the same name in the project/solution. I've been using visual studio for over 2 years but not doing webpages with it.
If you deploy your web site / application on a existing virtual directory, it ask you if you want to delete the existing content in it. I think you missed that check while deploying your application.
Related
In the office we have a server on the 'N' drive and we use IIS6 to create folders on our current domain which are then used as test directories for website building. Our website's domain is 'www.example.com' and sometimes, when I want to create a test environment for a new website, I'll go into IIS6, create a new directory e.g. 'test', make into into an application and then upload the website files and navigate to 'www.example.com/test' to find the website that I've built.
I've recently finished building a new website using ASP.NET MVC 4 platform, but I'm having a bit of trouble actually publishing it to a new directory that I've created e.g. 'test2'. I'm currently trying to publish it by right licking the project in VS 2012 and clicking publish before electing to publish the project using the 'file system' method and selecting the directory I wish to public to 'test2'. After clicking okay, the files are published okay but when navigating to 'www.example.com/test2', I get a 403 error message.
I'm obviously doing something wrong, so if anyone has any idea of what's going wrong I'd appreciate your help.
Thanks
I don't believe IIS 6 supports MVC
I have created an asp.net C# application developed in visual studio 2010, which is running without any error on my PC, but when i tried to run the same application on another computer with visual studio 2010, it gives following error,
The element 'buildProviders' cannot be defined below the application level.
Following article at http://forums.iis.net/t/1160248.aspx?The+element+buildProviders+cannot+be+defined+below+the+application+level+
You probably need to convert the virtual directory to application. I encountered this when deploying my app (using NancyFX).
You can open IIS Manager->Right-click the diretory of your web application->Click Convert to Application.
I faced this problem and i found out that somehow i had another version of my website within the subfolders of my webstie.
Meaning that my website is in a folder called "FrontEnd". Withing this folder there is a subforlder called backup that contains a backup of my website.
when i removed the backup folder, everything went ok.
If you recently upgraded your solution, check for the backup directory for crystal report within your solution. The backup directory can get created when you upgrade visual studio. To resolve this error, closed the solution. Went to the solution directory
and delete or move the backup directory to a different location outside of the solution directory. This solved the problem for me
You can fix this problem either defining the element in the web.config file of the root dir or setting Virtual Directory as APPLICATION in IIS.
For doing this with IIS 6.0, you first have to set the the directory in which your site is present as a Virtual Directory and then define this virtual directory as an Application.
All physical directories under Inetpub\Wwwroot are not considered applications until the following procedure is used:
Open IIS Manager.
Expand the Default Web Site node and look for the subdirectory that you want to designate as an application root.
Right-click the directory that you want to mark as an application root, and then click Properties.
On the Directory tab, in the Application Settings section, click Create.
In the Application name text box, type the name of the application, and then click OK.
The virtual directory is now an application root.
Maybe on oppening website you were selected upper project directory as website root
In my case, the issue was that the web.config inadvertently existed in a subfolder of the applications root folder. I had a "temp" subfolder, and I had placed a copy of the web.config there, unaware of the unintended side effects. The solution in my case was to remove the dup copy in the subfolder. Hth
(In my case name of project was repeating in directory )
The problem's solution is very simple: check its root directory in Solution Explorer. If there is a name folder within another name folder then this error will occur. Your web site contents should be very first after your web site name folder. In other words, contents should not display in another same name folder.
I have deployed NopCommerce to Windows azure website and I am able to see home page of NopCommerce website on website URL. After I login using admin credentials, I can see Administration link at the top. But when I click on the link, administration website is not shown.
It seems that with NopCommerce admin website does not get deployed. When I tried to publish from Admin website in Visual Studio to azure website, it didn't work. Can someone point me that how can I deploy admin website?
Run Deploy.bat in your root folder. This will create the entire website structure in the Deployable folder. FTP that up to your site.
It is quite tricky but will make sense to you after getting used to NopCommerce.
You need to create a subdirectory called 'Administration' and deploy there. Then you copy ALL the files that are inside /Administration/bin to /bin. These files will include Nop.Admin.dll and other dlls used by Admin.
Don't forget to copy all plugin DLLs to /plugins
If you add Nop.Admin project reference to Nop.Web it will be solved.
Just move Nop.Admin.dll to folder Nop.web\bin, this error is due to missing DLL Nop.Admin.dll from stuff.
For Publishing the NopCommerce Application website below is the step:
Step : 1 - Publish the Nop.Web project.
Step : 2 - Publish the Nop.Admin project.
Go to the publish folder where your publish created
Here is your answer below (Step :3 is your answer) :
Step : 3 - Cut all dll from the Administration and Paste all dll to bin folder which in main bin folder for whole project.
Step : 4 - Copy two things from your source project and in App_Data folder Settings.txt and InstalledPlugins.txt which is not published in your publish file so paste this two files in your publish folder in App_Data. (You need to change the connection string in Setting.txt as per your database host).
Step : 5 - Now you need to copy whole plugins folder from your source folder (but remember this plugins folder you need to copy from the Presentation folder not from the main source where the solution file are there.)and replace it to with your publish's plugin folder.
Step : 6 - Now your publish have been ready.(now you can deploy on hosting server)
If you're using web deploy via Visual Studio, make sure in your publishing settings you deploy as "RELEASE", else the admin directory will 404. Just thought I'd share after discovering this in version 3.30 myself...
You need to go to the properties of the Nop.Web project and go to the "Package/Publish Web" tab and under the "Items to deploy" set it to "All files in this project folder".
You need to do this for each "Configuration" you have that you deploy under as it will not set it as this on default for any new configurations you might have created.
The reason for needing this is because the admin project is outside of the Nop.Web scope. So the default setting of "Only files needed to run this application" only includes the Nop.Web files. If you select the "All files in this project folder", it will include the admin project because nop.web has references to it.
Hope this helps.
can any body suggest me how to remove the app_offline.htm file from application root directory in asp.net web application.when i run the page it doesnt show the design of html source
Go to Visual Studio 05/08 and open the solution explorer.
In the root folder there should be a folder named "App_offline.html". Right
click on it and delete it.
Re-open Visual Studio and you should be able to browse your page.
If you cannot find app_ofline.htm file in solution explorer, use windows explorer to get to the position of the solution and delete it manually. You can do it by rigth clicking to solution and clicking on "open folder in file explorer".
Just go to the root of your web directory, it should be there. it is something that VS puts there during certain tasks.
Solution for the problem
"This application is currently offline. To enable the application, remove the app_offline.htm file from the application root directory."
Go to your IDE (Visual studio)
Go on the solution Explorar in which site error is showing
RightClick and Delete that file.
How to solve this problem, when you got this error on the web page like as following image.
Solution 1
You can delete it from your project folder like as following picture , and then you can run your web page again, it will be okay .
To when running an ASP.NET app locally & receiving 'App is offline' small yellow bad screen. To resolve one set of steps maybe:
Visual Studio Solution Explorer select the file App_offline.html
'Exclude from Project' Right click and select
F5 - Build and Debug project again
The ASP.Net runtime environment checks the root of the application on the server for an “app_offline.htm” file and if it exists then it stops processing the new requests for the application and redirects the user to the “app_offline.htm” file to notify the user about the change.
So any time following message occurs
"This application is currently offline. To enable the application,
remove the app_offline.htm file from the application root directory."
Remove the magical file “app_offline.htm” from the Home directory
Go for the root folder and search app_offline.htm. You will get the file and just delete it and restart your visual studio
And i have indicated why this app_offline.htm is created
This is a .NET 2.0 "feature"
http://weblogs.asp.net/scottgu/archive/2005/10/06/426755.aspx
http://www.codeproject.com/KB/aspnet/app_offline.aspx
"The easiest way around this is to never publish directly to your server. You shouldn't anyway... Publish to a local folder then copy the site up"
Do you use Visual Studio? http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=102778
A short question.
I have a website running at :80.
I create a virtual directory "itemimages" under the site that reference E:\itemimages.
When i publish the ASP.net to the website at :80 with "Delete all existing files prior to publish" the virtual directory "itemimages" is also deleted.
Any way to stop this from happening?
Or better: Any way to define the virtual directory inside the asp.net application so i will be created in any "fresh" publish?
Thanks in advance!
Try publishing the website to the directory, as opposed to the website? I.e. publish to c:\Websites\WebsiteRoot (or whatever the path is), as opposed to http://www.sitename.com/
Or you could try using the "Replace files" instead of deleting all preexisting files ?