I am developing a .Net aspx application using visual studio 2012 and team foundation server/service paired with Microsoft azure cloud services.
I am able to edit code and check those changes back into TFS, however for some reason the entire /images folder which is important to this web application is no longer moving over to azure when being built.
The images exist in visual studio, can be viewed online on TFS but do not end up on our deployment server.
Have tried renaming the images folder, deleting it, checking new files in etc but still nothing shows in a web browser?
I do not have direct access to the azure account where this app is hosted, only TFS and the code base.
All changes to .aspx and .css files are turning up on azure server without a problem.
I will also say that when checking files in on visual studio it's very fast - almost like the files aren't being uploaded.
My background is in php development so I'm not denying this could well be user error.
In the Visual Studio project, make sure that the files in the images folder are marked as Build Action = Content in the properties window.
Related
The ASP.NET Web Forms Application that I've designed, contains a folder where the excel sheets that I require for the web reside. I've deployed the Web Application to AWS using the AWS Toolkit in the VS 2017, and could successfully get the application running over the Web. But, when I did something on the web (like Upload) which makes use of that folder, it resulted in exceptions and when I look at them through Log files later, I discovered that the Folders weren't even uploaded in the deploy process. Is there any way I could get the folder deployed as well?
Please ensure that the folder is included in your project before publishing. In Solution explorer, click on the Show All Files icon
And once the folder is displayed in the Solution Explorer, right click the folder and then Include in Project
when publishing to the Azure web site from visual studio site size 400MB I see in the azure portal that my site is almost 800MB...
I search all sub folders and I realize that inside the obj\Release\Package there is "PackageTmp" which contain the all site with all my folders (some of them big files for download).
The question is why asp.net need the site twice ?
can i simply remove the obj folder with ftp app and the site will be ok ?
I Need more size it's not fair to scale becuase of that...
When you deploy from Visual Studio, you are using msdeploy. Normally, that should not be copying obj\Release\Package to the Azure Web App.
To check what's in your Azure Web App, it's best to use Kudu Console. In there, go to your D:\home\site\wwwroot folder, and check what files are there. Are you really seeing an obj\Release\Package folder in there (i.e. D:\home\site\wwwroot\obj\Release\Package`)?
If that's not where you see it, please provide more details:
what version of VS?
what type of app are you deploying (e.g. is it an MVC app)?
are you deploying debug or retails?
So I'm using visual studio 2010 to build a website that was formerly running on PHP, so I'm pretty new to the environment.
In starting the project I built a website project, not a web application project. I know that will probably generate a lot of "never use a website project, use a web application project instead" comments, but bear with me.
I'm attempting to provide our server team with the necessary files to compile on our server for the first time. However they're used to working with web application files, not website files.
Normally they are given the source code and a batch file that compiles the code into deployment directories and then they just move the files to the server from there. I'm pretty sure that the other teams use deployment packages to do this, which obviously isn't an option for a website.
My question is, what would be the equivalent steps for getting the source for a website ready to deploy vs a web application? I have published the website to a separate folder and this has rendered what I think is the equivalent in many ways, but I wanted to make sure.
Also, is it possible to publish certain parts of a website without others?
Please with-hold all the comments about how I should be using a web application instead, google seems to assume that's all that's used out there too.
Thanks!
There isn't much to deploying a web site other than copying the source files to a directory in IIS. It will compile the site automatically on the first page request.
I agree with Britton. I personally prefer web application but with the web site project you have 2 options.
Either a) Upload all the files (including the .vb or .cs files) and the web server will compile on the fly. OR, you can publish to a separate folder locally on your machine, and then upload that folder. I would do the publish if you don't want anyone seeing your source code.
I have an ASP.NET application that has two very large folders within the application on the production side: One for images and another for App_Themes. They grow dynamically from user input and customization. There are similar folders in my dev application, which have only some sample data for testing.
I am using web deploy through Visual Studio 2010 to publish my site to the production server. I have changed my .csproj file settings to exclude these two folders from deployment and have also checked the "leave extra files on destination" checkbox. However, the publishing still takes a long time. I think the reason is related to web deploy checking all the files in the images folder and the App_Themes folder on the server.
Is there a solution that would solve the publishing problem? I would like to continue using web deploy because it is really practical compared to other methods of publishing. The server is running IIS 6.
You can publish the way you're doing it, but into a local directory. It should be quick that way. Then set up a robocopy job ( http://en.wikipedia.org/wiki/Robocopy ) to sync the local publish directory with the web server. Robocopy can be fired off via a .bat file (I bet you can even chain it somehow to the completion of the publish) and is very configurable allowing you to specify files or directories to omit.
I have an ASP.Net website that I built in a computer science class. I built it in Visual Studio and the solution is on my local drive. How would I deploy this to a real website?
You will need to do a few things.
You will need to get a hosting account that supports ASP.NET
From there you can use the "Publish" option from within Visual Studio under the "Build" menu option to push out a copy of the site.
When publishing you should publish in release mode.
Get hosting that supports the version of .NET and ASP.NET you have used and copy the files over.
Assuming that already you have an IIS application and web folder set up on a web server somewhere, the simplest method goes like this:
In Visual Studio, right-click on the web application project, and click Publish.
Select File System as the publish method.
Select a target location. This is where the publishable files will be placed. Use c:\pub or something similar.
Hit Publish
Once the publish operation is done, copy everything in c:\pub (or whatever target folder you used in step 3) to your web folder on the web server. Depending on your server accessibility, you may need to do this via FTP.
You might also investigate ClickOnce Deployment if your server supports it.
If you don't already have server space, you'll need to find a good hosting provider that supports ASP.NET. Google has many suggestions.