Last post May 01, 2017 05:23 PM by bbcompent1
Apr 20, 2017 02:05 PM|Endeavor|LINK
Is there no longer a way to create a website project in 2017 community. All I can find is website application. I need the to be able to update pages without having to recompile the entire site. Thanks.
Apr 20, 2017 04:30 PM|bbcompent1|LINK
Let me do some digging, it may have been deprecated. As far as I know you do not need to compile your website to deploy it. You can leave it uncompiled and it should still run. But just in case, let me do some digging and I'll get back to you.
Apr 20, 2017 04:37 PM|bbcompent1|LINK
Try looking here:
Apr 20, 2017 04:49 PM|PatriceSc|LINK
I still see "Project..." and "Web site..." (as well as "File.." and "Project From Existing Code...") in my "File", "New" menu...
This is VS Community 2017 15.1 (26403.7). Could it be that you are using a preview or at last an older version?
Apr 20, 2017 06:18 PM|Endeavor|LINK
OK thanks for the information. I see what my problem was. To start a new website I have to use the file new website to get to the new website window. The start page doesn't give the choice to start a new website, it just give the options to Open project
, open folder, and open website. Thanks for your help.
I would still be interested to know if a Website Application can be deployed without having to be compiled because everything I have read is that it needs to be compiled on the development site before it can be deployed to the production site and a website
project can be deployed to the production server without being compiled. Thanks again.
Apr 20, 2017 08:02 PM|PatriceSc|LINK
Try perhaps https://msdn.microsoft.com/en-us/library/dd547590(v=vs.110).aspx for all the details.
If you really want to deploy and compile source code on your server, the easiest path is likely to use a web site project. If I remember the App_Code folder might still work in a WAP (but I never tried as I'm rather in the precompilation camp).
If it really worth, you perhaps have other options with ASP.NET extensibility or tools. Not sure what is the exact benefit you are trying to get. You really have to deploy source code rather than DLLs ? ( you can compile a WAP into multiple DLLs rather than
to a single DLLs. Also the ASPX markup can be kept as being updatable).
Edit: I was thinking about something such as
Apr 21, 2017 10:47 AM|bbcompent1|LINK
Yeah, what we used to do in my old department is just copy everything up to the web server with the exception of the project and solution files. That allowed us to run the site like it was a website project rather than an application. You will notice potential
speed degradation since it will not be using a code-behind dll file.
May 01, 2017 05:23 PM|bbcompent1|LINK
There is a way, the naming convention has changed. Take a look at this TechNet article and get back to me if you need more help.