简体   繁体   English

Umbraco,ASP.NET进行远程开发的方法

[英]Method for Remote Development with Umbraco, ASP.NET

My setup is as follows [Home Network, Dreamspark Software] : 我的设置如下[家庭网络,Dreamspark软件]:

  • Local workstation w/ Visual Studio 2015 Preview 带有Visual Studio 2015预览的本地工作站
  • Server VM 1 - Windows 2012 w/ SQL Server 服务器VM 1-Windows 2012 w / SQL Server
  • Server VM 2 - Windows 2012 Web Server / IIS Server VM 2-Windows 2012 Web服务器/ IIS

I am traditionally only experienced with C# application development. 传统上,我只有C#应用程序开发经验。 I would like to dive into an ASP web application I have in mind and want to use Umbraco as the site's framework. 我想深入了解一个ASP Web应用程序,并希望将Umbraco用作站点的框架。

What I need clarification on are the logistics of the development environment vs. the IIS server. 我需要澄清的是开发环境与IIS服务器之间的关系。

I think ultimately I'd love to develop inside the Visual Studio IDE but at compile time have everything automagically publish to the IIS server. 我认为最终我希望在Visual Studio IDE中进行开发,但是在编译时,所有内容都会自动发布到IIS服务器。

I see online that the typical method is to locally install SQL and IIS express with Umbraco, develop locally, and then xcopy out to the IIS server. 我在网上看到典型的方法是使用Umbraco在本地安装SQL和IIS Express,在本地进行开发,然后将xcopy复制到IIS服务器。

Is there any way to avoid that? 有什么办法可以避免这种情况? It seems kludgy and wasteful. 看起来很笨拙而且浪费。 I'd rather just use the IDE locally and have everything push out to IIS server. 我宁愿只在本地使用IDE,并将所有内容推送到IIS服务器。

Thanks in advance! 提前致谢!

I believe you don't understand a main drawback with your development flow: what about debugging ? 我相信您不了解开发流程的主要缺点: 调试呢?

If you directly publish it to remote Web server (IIS), you won't be able to debug your code locally (you'll need to use the Visual Studio Remote Debugger, which doesn't work exactly as the local debugger), and whenever you need to test some advancement or improviement in your site, you'll need to publish it (think about the time that takes uploading files to your server). 如果直接将其发布到远程Web服务器(IIS),则将无法在本地调试代码(您将需要使用Visual Studio远程调试器,该功能不能与本地调试器完全一样),并且每当您需要在网站上测试某些改进或改进时,就需要发布它(考虑将文件上传到服务器的时间)。

Also, if you would automagically-publishing your site after every local build in Visual Studio, you might be uploading untested code to production. 另外,如果在Visual Studio中进行每个本地构建后自动发布站点,则可能会将未经测试的代码上传到生产环境中。 You would end up configuring another SQL Server and IIS Windows servers in order to have a production and development environment (actually, you'll need this anyway, because you don't want to excuse yourself with your user base saying that current release of your site works on your machine - who cares ;) -). 您最终将配置另一台SQL Server和IIS Windows服务器,以具有生产和开发环境(实际上,无论如何您都将需要这样做,因为您不希望自己的用户群对您说当前版本该站点在您的机器工作 -谁在乎;)-)。

Usually, you've the whole SQL Server and IIS installed in your local machine and whenever you re-compile your solution, a F5 in your local machine's Web browser will be enough to check that your code is working as you expect. 通常,您已经在本地计算机上安装了整个SQL Server和IIS,并且每当您重新编译解决方案时,在本地计算机的Web浏览器中使用F5足以检查您的代码是否按预期工作。

After you've some project goals finished, you upload your site using WebDeploy feature available on Visual Studio. 完成一些项目目标之后, 您可以使用 Visual Studio上可用的WebDeploy功能上载网站 Once you've configured this, uploading your site to your server is just about one click! 一旦配置完成,将您的站点上传到服务器只需单击一下!

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM