Hi Steven
I confirm that what I have is a VS2003 web project converted to VS2005 on
Vista.
On looking at various posts, I see a vein suggesting that it could be
firewalls that are at the root of the problem. With that in mind I turned
off the firewall completely, detached from the web and used my notebook in
standalone mode.
All I want to be able to do is use localhost or the internal web server to
display a web page so that I can confirm that what I have done so far is OK
before progressing to the next bit of development. I could do this in VS2003
by using Browse or Browse with from the Solution Explorer or from IIS by
selecting the aspx file to browse and browsing it. What I see the browser
doing is attempting to browse but at the end abandoning with the message
"Navigation to the webpage was canceled". It has what appears to me to be a
permissions or access issue. As far as I can see there is nothing external
to the machine that needs to be reached, so access may be out of the picture.
That leaves permissions.
With that in mind, I opened IE and reset security to default for all
catagories. I now get the error message "Debugging is not supported under
current trust levels". With the thought that I may have touched and upset
settings in VS and/or IE and/or IIS that VS depends on, I am re-installing
VS2005 to see if anything at all is different.
I am groping in the dark a bit really and wasting too much valuable time to
get back to the point where I was on XP SP1.
What intrigues me is that a simple HTML page works, while an aspx page does
not. The aspx page is based on a master page with 4 ContentPlaceHol ders set
in a table structure. Two of the ContentPlaceHol ders use images and TreeView
menus, with one containing just an image and the final one being a
placeholder for page content. I have replaced 3 VS2003 user controls with
html in the ContentPlaceHol ders and the designer showns this correctly. This
is then used by a WebForm which for three of the ContentPlaceHol ders is told
to use the Master leaving the last for the page body content to be filled in
the aspx page. At this point I want to view what the page looks like, so try
to browse. No items in the TreeView menu are linked so nothing is active.
This is just about look and feel. It is a wholly new page although some html
has been cut and pasted from the former VS2003 project. All errors and
warnings raised by the iDE for the converted project have been resolved.
I am unable to browse successfully either with IE or the internal browser.
Yet this aspx page is just a glorified html page with some asp.net components.
Before I moved the web project from VS2003 to VS2005, I has started a revamp
of the assemblies used by the middle tiers and a large expansion of the data
model in SQL Server. The amount of change is quite comprehensive and for
the most part has been unit tested. It is no longer worth the effort to try
to get this working with the VS2003 user interface, so I have migrated the
middle tier objects to VS2005. The master page was to put in place a common
menu structure for the site, leaving just the content to be placed in the
ContentPlaceHol der. That however is a side issue as none of these objects
are instantiated at the point where I am attempting to browse.
I will post again when I have re-installed the devenv.
cheers
--
PeterW
"Steven Cheng[MSFT]" wrote:
Hi Peter,
From your description, you got some problems when try running asp.net
pages(converted from vs 2003 project to VS 2005 one) on Vista box, correct?
Since I haven't found any existing or know issue on this, I think we can
first test to confirm whether it is a machine or environment specific one.
I suggest you test the following things and check the behavior:
1. directly deploy the converted web application in IIS virtual directory
and run it (without vs 2005) to see whether it work
2. You can also try start the vs 2005 testserver from commandline to host
an ASP.NET 2.0 application. You can use this approach to test whether the
testserver is ok:
http://weblogs.asp.net/scottgu/archi...21/431138.aspx
3. Regardless of the vs 2003 converted project, you can try a completely
new created ASP.NET 2.0/VS 2005 web site project to see whether it works.
If you have any other finding, please also feel free to post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
=============== =============== =============== =====
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.