自动部署的Win App - Vista IIS 7.0 [英] Autodeployed Win App - Vista IIS 7.0

问题描述

我创建了一个三层应用程序，包括Client（Exe和

Exe.Config），Middle（WebServices）和Database层。客户端层

包含Exe，Exe.Config和动态Web引用。 Exe从Exe.Config文件中读取一个

键值对，该文件是指向它应连接的相应

WebService的链接，并设置动态Web referencea ?? s

URL。如果Exe.Config文件不包含键值，或者如果找不到

Exe.Config，则动态Web引用尝试建立

连接到默认WebService，在开发

机器上指定。 WebService有一个Web.Config文件，其中包含指向数据库的

ConnectionString。


我已自动部署此应用程序（客户端和中间层）在一台带有IIS的Windows 2000服务器上.5。从我的Windows XP机器（带有IIS 5）我可以使用以下URL来运行这个应用程序： br /> http：//myServer/myApps/myApp.Exe 。此外，它连接到Exe.Config文件中的WebServices Ia ?? ve $ / b
。


我升级了另一台Windows XP机器（使用IIS 5）使用IIS 7.0运行Vista。

当我在这台机器上运行应用程序时，使用与上面相同的URL，它会尝试连接到默认的WebService（我的开发WebService） ）。

Ita ??表现得好像无法找到或无法读取服务器上的Exe.Config。

我是否必须制作IIS 7.0中的任何更改，以允许应用程序读取和

下载不是本地的Exe.Config文件？有什么建议吗？


提前致谢。

I have created a three tier application consisting of Client (Exe and
Exe.Config), Middle (WebServices) and Database tiers. The Client tier
contains an Exe, an Exe.Config and a dynamic Web reference. The Exe reads a
key-value pair from the Exe.Config file, which is a link to the appropriate
WebService that it should connect to, and sets the dynamic Web referencea??s
URL. If the Exe.Config file does not contain the key-value or if the
Exe.Config is not found, the dynamic Web reference tries to establish a
connection to the default WebService, as specified on the development
machine. The WebService has a Web.Config file which contains a
ConnectionString pointing to the Database.

I have auto-deployed this application (the Client and Middle tiers) on a
Windows 2000 server with IIS 5. From my Windows XP machine (with IIS 5) I can
run this application just fine using a URL such as:
http://myServer/myApps/myApp.Exe. Also, it connects to the WebServices Ia??ve
setup in the Exe.Config file.

I upgraded another Windows XP machine (with IIS 5) to Vista with IIS 7.0.
When I run the application on this machine, using the same URL as above, it
attempts to connect to the default WebService (my development WebService).
Ita??s behaving as if it cana??t find or cana??t read the Exe.Config on the server.
Do I have to make any changes in IIS 7.0 to allow the application to read and
download Exe.Config files that are not local? Any suggestions?

Thanks in advance.

推荐答案

我应该补充三点层Windows应用程序是在.NET Framework 1.1 SP 1上使用

Visual Studio 2003开发的。


" NormD"写道：

I should add that the three tier Windows application was developed using
Visual Studio 2003 on .NET Framework 1.1 SP 1.

"NormD" wrote:

我创建了一个三层应用程序，包括Client（Exe和

Exe.Config），Middle（WebServices）和Database层。客户端层

包含Exe，Exe.Config和动态Web引用。 Exe从Exe.Config文件中读取一个

键值对，该文件是指向它应连接的相应

WebService的链接，并设置动态Web referencea ?? s

URL。如果Exe.Config文件不包含键值，或者如果找不到

Exe.Config，则动态Web引用尝试建立

连接到默认WebService，在开发

机器上指定。 WebService有一个Web.Config文件，其中包含指向数据库的

ConnectionString。


我已自动部署此应用程序（客户端和中间层）在一台带有IIS的Windows 2000服务器上.5。从我的Windows XP机器（带有IIS 5）我可以使用以下URL来运行这个应用程序： br /> http：//myServer/myApps/myApp.Exe 。此外，它连接到Exe.Config文件中的WebServices Ia ?? ve $ / b
。


我升级了另一台Windows XP机器（使用IIS 5）使用IIS 7.0运行Vista。

当我在这台机器上运行应用程序时，使用与上面相同的URL，它会尝试连接到默认的WebService（我的开发WebService） ）。

Ita ??表现得好像无法找到或无法读取服务器上的Exe.Config。

我是否必须制作IIS 7.0中的任何更改，以允许应用程序读取和

下载不是本地的Exe.Config文件？有什么建议吗？


提前致谢。

I have created a three tier application consisting of Client (Exe and
Exe.Config), Middle (WebServices) and Database tiers. The Client tier
contains an Exe, an Exe.Config and a dynamic Web reference. The Exe reads a
key-value pair from the Exe.Config file, which is a link to the appropriate
WebService that it should connect to, and sets the dynamic Web referencea??s
URL. If the Exe.Config file does not contain the key-value or if the
Exe.Config is not found, the dynamic Web reference tries to establish a
connection to the default WebService, as specified on the development
machine. The WebService has a Web.Config file which contains a
ConnectionString pointing to the Database.

I have auto-deployed this application (the Client and Middle tiers) on a
Windows 2000 server with IIS 5. From my Windows XP machine (with IIS 5) I can
run this application just fine using a URL such as:
http://myServer/myApps/myApp.Exe. Also, it connects to the WebServices Ia??ve
setup in the Exe.Config file.

I upgraded another Windows XP machine (with IIS 5) to Vista with IIS 7.0.
When I run the application on this machine, using the same URL as above, it
attempts to connect to the default WebService (my development WebService).
Ita??s behaving as if it cana??t find or cana??t read the Exe.Config on the server.
Do I have to make any changes in IIS 7.0 to allow the application to read and
download Exe.Config files that are not local? Any suggestions?

Thanks in advance.

您好NormD，


我根据你的描述进行了连续测试，确实看到了问题

在我身边。


当我放置我的测试应用程序时（带有exe） .config）在IIS 5上，然后

使用URL启动应用程序，例如：

http：//localhost/TestApp/TestApp.exe


应用程序可以访问exe.config文件Web服务器。

但是，当我将应用程序放在IIS 6或7上，然后使用URL输出

应用程序时，应用程序无法访问exe.config文件

在Web服务器上，所以它使用设置的默认值。


我使用一个名为''Fiddler''的工具来观看对&来自

IIS 7的回复。我发现每次应用程序将对IIS 7的请求汇总到IIS 7时，IIS 7的响应总是为403 ''禁止''。

如果我修改URL直接请求exe.config文件，例如：

http：//localhost/TestApp/TestApp.exe.config


回复也是403''禁止''。


默认情况下IIS高于6.0会阻止.config文件，因为这些文件可能包含敏感信息用户名

和密码等信息。


我将继续研究如何在IIS 6或7上更改此行为，

并尽快将结果发回给您。


我感谢您的耐心等待！


此致，

Linda Liu

Microsoft在线社区支持


=== ===============================================

通过电子邮件收到我的帖子通知？请参阅
http://msdn.microsoft .com / subscripti ... ult.aspx＃notif

ications。


注意：MSDN托管新闻组支持服务是针对非紧急问题

如果社区或微软支持人员在1个工作日内做出初步回复是可以接受的。请注意，每个跟随

的响应可能需要大约2个工作日作为支持

专业人士与您合作可能需要进一步调查才能达到

最有效的分辨率。该产品不适用于需要紧急，实时或基于电话的交互或复杂的b $ b项目分析和转储分析问题的情况。这种性质的问题最好通过联系

Microsoft客户支持服务（CSS）处理
href =http://msdn.microsoft.com/subscriptions/support/default.aspx\"target =_ blank> http://msdn.microsoft.com/subscripti...t/default.aspx 。

======================================== ==========


此帖子按原样提供。没有保证，也没有授予任何权利。

Hi NormD,

I performed serial tests based on your description and did see the problem
on my side.

When I place my test application(with a exe.config) on IIS 5, and then
launch the application with a URL, such as:

http://localhost/TestApp/TestApp.exe

the application could access the exe.config file on the web server.
However, when I place the application on IIS 6 or 7, and then lauch the
application with a URL, the application couldn''t access the exe.config file
on the web server, so it uses the default value of the settings.

I use a tool called ''Fiddler'' to watch the requests to & responses from the
IIS 7. I found that every time the application sumbits a request for the
exe.config to the IIS 7, the response from IIS 7 is always 403 ''Forbidden''.
If I modify the URL to request the exe.config file directly, such as:

http://localhost/TestApp/TestApp.exe.config

The response is also 403 ''Forbidden''.

It seems that IIS higher than 6.0 block the .config file by default,
because these files may contain sensitive information such as user names
and passwords.

I will go on the research about how to change this behavior on IIS 6 or 7,
and will get the result back to you ASAP.

I appreciate your patience!

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Linda，


我在Vista机器上运行Fiddler作为好吧，从Web / app服务器和localhost运行应用程序

，并注意到一些奇怪。

Fiddler没有捕获localhost的流量（即
http：//localhost/MyDir/MyApps/MyApp.exe）。但是，当我从服务器运行应用程序时，它确实捕获了流量

（即
http：//myServer/myApps/myApp.Exe) 。

我注意到Fiddler没有捕获myApp.Exe的请求.Config
这台机器上的
文件，就像在我的XP机器上一样。此外，我检查了web / app服务器上的

IIS日志，发现在Vista计算机上运行的应用程序请求了myApp.Exe.Config文件

，它可能是

返回（日志包含状态代码200（= OK））。与您发现的
相反，当我在Internet Explorer中请求myApp.Exe.Config文件时，我做了

收到完整的XML。


此外，为了确认你找到了什么，从localhost运行应用程序

Vista也没有使用Exe.Config文件。


谢谢。


Linda Liu [MSFT]"写道：

Linda,

I ran Fiddler on the Vista machine as well, while running the application
from the Web/app server and from localhost, and noticed some weirdness.
Fiddler didn''t capture traffic for localhost (i.e.
http://localhost/MyDir/MyApps/MyApp.exe). However, it did capture traffic
when I ran the application from the server (i.e.
http://myServer/myApps/myApp.Exe).

I noticed that Fiddler did not capture the request for the myApp.Exe.Config
file on this machine, as it does on my XP machine. Furthermore, I checked the
IIS logs on the web/app server and noticed that the myApp.Exe.Config file was
requested, by application running on the Vista machine, and it probably was
returned (the logs contained a status code 200(=OK)). Contrary to what you
found, when I requested the myApp.Exe.Config file in internet explorer I did
receive the complete XML.

Also, to confirm what you found, running the application from localhost on
Vista did not use the Exe.Config file either.

Thanks.

"Linda Liu [MSFT]" wrote:

嗨NormD，


我根据你的描述进行了连续测试，确实看到了问题

在我身边。


当我在IIS 5上放置我的测试应用程序（带有exe.config），然后

启动应用程序使用URL，例如：

http：// localhost / TestApp /TestApp.exe


应用程序可以访问Web服务器上的exe.config文件。

但是，当我放置应用程序时IIS 6或7，然后带有URL的

应用程序，应用程序无法访问Web服务器上的exe.config文件

，因此它使用设置的默认值。


我使用一个名为Fiddler的工具来查看对&来自

IIS 7的回复。我发现每次应用程序将对IIS 7的请求汇总到IIS 7时，IIS 7的响应总是为403 ''禁止''。

如果我修改URL直接请求exe.config文件，例如：

http：//localhost/TestApp/TestApp.exe.config


回复也是403''禁止''。


默认情况下IIS高于6.0会阻止.config文件，因为这些文件可能包含敏感信息用户名

和密码等信息。


我将继续研究如何在IIS 6或7上更改此行为，

并尽快将结果发回给您。


我感谢您的耐心等待！


此致，

Linda Liu

Microsoft在线社区支持


========== ========================================

获取通知通过电子邮件到我的帖子？请参阅
http://msdn.microsoft .com / subscripti ... ult.aspx＃notif

ications。


注意：MSDN托管新闻组支持服务是针对非紧急问题

如果社区或微软支持人员在1个工作日内做出初步回复是可以接受的。请注意，每个跟随

的响应可能需要大约2个工作日作为支持

专业人士与您合作可能需要进一步调查才能达到

最有效的分辨率。该产品不适用于需要紧急，实时或基于电话的交互或复杂的b $ b项目分析和转储分析问题的情况。这种性质的问题最好通过联系

Microsoft客户支持服务（CSS）处理
href =http://msdn.microsoft.com/subscriptions/support/default.aspx\"target =_ blank> http://msdn.microsoft.com/subscripti...t/default.aspx 。

======================================== ==========


此帖子按原样提供。没有保证，也没有授予任何权利。

Hi NormD,

I performed serial tests based on your description and did see the problem
on my side.

When I place my test application(with a exe.config) on IIS 5, and then
launch the application with a URL, such as:

http://localhost/TestApp/TestApp.exe

the application could access the exe.config file on the web server.
However, when I place the application on IIS 6 or 7, and then lauch the
application with a URL, the application couldn''t access the exe.config file
on the web server, so it uses the default value of the settings.

I use a tool called ''Fiddler'' to watch the requests to & responses from the
IIS 7. I found that every time the application sumbits a request for the
exe.config to the IIS 7, the response from IIS 7 is always 403 ''Forbidden''.
If I modify the URL to request the exe.config file directly, such as:

http://localhost/TestApp/TestApp.exe.config

The response is also 403 ''Forbidden''.

It seems that IIS higher than 6.0 block the .config file by default,
because these files may contain sensitive information such as user names
and passwords.

I will go on the research about how to change this behavior on IIS 6 or 7,
and will get the result back to you ASAP.

I appreciate your patience!

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

这篇关于自动部署的Win App - Vista IIS 7.0的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！