升级后的Web服务从VS2003升级到VS2005，所有Hell都松了！ [英] Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
问题描述
好的，我会事先承认 - 我只是没有得到它。
这是我们以前的VS2003开发模型。开发人员在自己的工作站上开发WS
解决方案，使用他们自己的IIS Web服务器映射到本地devleopment文件夹。项目编译为子文件夹.\bin。为了
部署，asmx页面和bin子文件夹被复制到生产服务器。
现在我升级到VS2005。好的，所以除了名字，一切都是
改变了。没有更多的项目文件，代码隐藏页面被移动到子文件夹，
导致转换本身打嗝。好的，我可以顺便说一句。但是在哪里
到底是构建的二进制文件???
这里是我在.sln文件中的目标路径：
Release.AspNetCompiler.TargetPath =" C：\ VBBjects \SRSDev \ Source Code \ SWS
Components \bin"
所以我点击Build |重建解决方案：
重建全部开始...
重建全部成功
但是这里是'输出文件？？？ bin文件夹是空的!!!
请尽可能帮忙。谢谢!!!
- Joe Geretz -
OK, I''ll admit it up front - I just don''t get it.
Here''s our previous VS2003 development model. Developers develop the WS
solution on their own workstations, using their own IIS web servers mapped
to the local devleopment folder. Project compiles to a subfolder .\bin. To
deploy, the asmx page and bin subfolder are copied to the production server.
So now I upgrade to VS2005. OK, so except for the name, everything is
changed. No more project file, codebehind pages are moved into a subfolder,
causing the conversion itself to hiccup. OK, I can get by that. But where
the hell is the binary file being built???
Here''s my target path in the .sln file:
Release.AspNetCompiler.TargetPath = "C:\VBProjects\SRSDev\Source Code\WSL
Components\bin"
So I hit Build | Rebuild Solution:
Rebuild All started...
Rebuild All succeeded
But where''s the output file??? The bin folder is empty!!!
Please help if you can. Thanks!!!
- Joe Geretz -
推荐答案
其他信息：
当我从Visual Build Pro批量编译时，我收到以下错误：
ASPNETCOMPILER：错误ASPRUNTIME：预编译目标目录
（C：\ VBBProjects \SRSDev \ Source Code \ SWS Components \bin \）不能与源应用程序目录（C：\ VBBjects）位于同一个
树中\\ SRSDev \Source
Code\WSL Components\）。
现在可能，这是一个阻止
交互式编译的二进制输出。你会期望交互式的
编译得到与批量编译一样的反馈！ ：-\
好的，那么这里的交易是什么？他们是说用VS2005我们不能用
构建项目，以便项目文件夹是相同的文件夹映射
作为Web服务的虚拟文件夹？为什么他们会改变这个？
新的最佳实践是什么？我想做的就是从
VS2003升级到VS2005。
很好，所以我不会打这个东西。我将目标路径更改为
Release.AspNetCompiler.TargetPath =" .. \ WSL Precomp\SRSFreedom"。好的，
构建成功，但是这是什么？看起来我的解决方案在目标位置有一个完整的副本
，包括应用程序DLL的
（谁的名字全部都是顺便改变了）。所以我真的很担心
这个。这是我的网站应该映射的地方吗？如果是这样，他们为什么要把它们称为预编译目录？ （谈论矛盾 - 是这个目标（意味着结束点，或者这是一个预编译
文件夹？）这是怎么回事？
/>
< rant>
为什么微软似乎有这样做的既得利益！@＃
Additional info:
When I compile in batch from Visual Build Pro, I get the following error:
ASPNETCOMPILER : error ASPRUNTIME: The precompilation target directory
(C:\VBProjects\SRSDev\Source Code\WSL Components\bin\) cannot be in the same
tree as the source application directory (C:\VBProjects\SRSDev\Source
Code\WSL Components\).
Now presumably, this is the same error which is preventing the production of
the binary output from the interactive compile. You''d expect the interactive
compile to give the same feedback as the batch compile does! :-\
OK, so what''s the deal here? Are they saying that with VS2005 we can''t
structure the project so that the project folder is the same folder mapped
as the virtual folder for the web service? Why would they change this?
What''s the new best practices? All I want to do is get this upgrade from
VS2003 to VS2005.
Fine, so I''m not going to fight this thing. I change the target path to
Release.AspNetCompiler.TargetPath = "..\WSL Precomp\SRSFreedom". OK, the
build succeeds, but what''s this? It looks like the there''s an entire replica
of my solution at the target location, including the application DLL''s
(who''s names have all changed by the way). So I''m really confused about
this. Is this where my web site is supposed to be mapped? If so, why to they
call this a ''precompilation taget directory''? (Talk about an oxymoron - is
this the target (implies the end point, or is this a pre-compilation
folder?) What is this all about?
<rant>
Why does Microsoft seem to have a vested interest in making this so !@#
^ ％＃
对其客户来说很难??? !!!我的意思是他们想要开发者观众
或者不是吗？我还有其他问题需要解决这里和这个
^%#
difficult for its customers???!!! I mean do they want the developer audience
or don''t they? I have other issues to wrestle with here and this
@％
这篇关于升级后的Web服务从VS2003升级到VS2005，所有Hell都松了！的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
