WilsonDotNet Forums : Visual Studio

Problem with Visual Web Developer 2005

Sun, 03 Sep 2006 17:43:05 GMT

There's a Start New Thread link above the grid in each forum.

There were some changes in the ASP.NET v2.0 designer, so things that worked in the designer in v1.* may not work in v2.0 in the designer. My MasterPages for v1.* was affected by that, but I don't view this as something to worry about since ASP.NET v2.0 includes the real deal. That's right, while you certainly can continue to use my version in v2.0 (without the designer, and it may not auto-convert well), that's not really the intent. The whole point of my MasterPages was to get a decent solution to templating in v1.* that would "convert" decently well to the real deal in v2.0. And by "convert" I mean that its similar enough that it won't take long at all to make the appropriate changes, not that MS's auto-converter will do it for you. So I really really really recommend that you switch to the real MS MasterPages in v2.0 -- its far better in the designer than anything any non-MS person can implement, and its also far better optimized and has other goodies that no non-MS person could do.

Thanks, Paul Wilson

Problem with Visual Web Developer 2005

Sun, 03 Sep 2006 17:35:12 GMT

Hello Paul,

This is not really a reply to the post but a new question; but I can't seem to find how to start a new post/thread. I dont have my user ID and Passoword but have a legit copy of your software.

I use the Wilson.WebControl to use the concept of a masterpage in Dotnet 1.0. Now that I'm trying to upgrade to Dotnet 2.0 there seems to be an issue with the the masterpage object that I don't know how to overcome.

The issue is that in the design view; there is an error to the effect that the "MasterPage1 Object reference not set to an istance of an object".

The .cs file after the upgrade looks significantly different i.e where I had defined an instance of the MasterPage as MasterPage1 is no longer there (the line of code disappeared after the uypgrade) and if I try to add it the complier complains that object reference already exists.

Please help

Thanks

Ankur

Debugger Problem Solved

Fri, 30 Jun 2006 10:20:27 GMT

I had the same problem. I had a file called Album.cs in my BizLogic project, and a file called Album.cs in my DataAccess project. And when I setup a debug point in the Album.cs of the DataAccess project, the debugger would go all over the Album.cs of the BizLogic project.

After looking at this thread, I renamed the Album.cs of the DataAccess project to AlbumDAL.cs, and now it works like a charm.

Intellisense dissapeared

Sun, 11 Sep 2005 18:34:22 GMT

I've not been able to determine the exact conditions when this occurs. The best solution is to get ReSharper but if you don't want to shell out extra money, you can do a couple of things that work some of the time.

One is to shut down VS.NET. Delete the contents of the bin folder. Restart VS.NET and rebuild.

I've seen another solution involving the .suo file but haven't really seen that one work for me.

Unfortunately, I have a page or two where the intellisense still gets messed up shortly after editing them even when doing the cleanup mentioned above.

-George Hicks

Debugger Problem Solved

Fri, 17 Jun 2005 01:50:16 GMT

Cheers - manually editing the .vbproj file worked for me, nothing else would :)

Intellisense dissapeared

Thu, 09 Jun 2005 01:29:45 GMT

Hello,

can anyone help me out with this one?

Suddenly I lost the IntelliSense function when creating an aspx-page in Visual Studio.

On this forum I found a post handling the same problem and the solution that was proposed is writing everything between <body></body> tags. But my problem is that I already had everything between those tags, that everything worked fine untill suddenly it didn't anymore. I also can't switch between HTML and Design view anymore. This is not something I'm missing, because I never work in the design view, but maybe it can help you guys figuring out what's wrong with it. And in the HTML editor toolbar, I can't on the "format the whole document" and "validate the document" buttons anymore...

Thank you very much in advance.

Debugger Problem Solved

Thu, 19 May 2005 03:15:21 GMT

hi

i am currently experiencing the same breakpoint issue. my scenario is a bit diffrent tho.Im trying to debug classis ASP pages. if i add a ASPX page to my project the breakpoints work 100% but as soon as i set a breakpoint in ASP it doesnt work.let me also add that the ASP debugging use to work. i then created a second ASP web application to mimic the 1st working ASP.NEt app but the second app project refuses to go into debug mode for classis ASP code.

VS .NET 2003 won't close for asp.net project

Fri, 15 Apr 2005 04:40:37 GMT

I wish I could suggest something, but I've never seen or heard of a problem like that. Do you have the original files so that you can do a diff?

Good luck, Paul Wilson

VS .NET 2003 won't close for asp.net project

Thu, 14 Apr 2005 22:31:36 GMT

I have built several ASP.NET projects with success. For one of them, it loads and runs fine but when I go to close Visual Studio, VS hangs. I eventually get "... application not responding. End Now or Cancel". This doesn't happen with my other projects which contain similar pages and code.

The project in question is one that I delivered to a client several months ago. At that time I was not experiencing this problem. The problem has only occurred since the client sent me back the project files for some changes. The client is also experiencing the same problem.

My virus scan hasn't detected any viruses in the files the client sent me.

Can you suggest what I should look for to determine what is causing the problem or suggest ways to fix this?

Thank you in advance.

ZLA

Debugger Problem Solved

Wed, 01 Sep 2004 03:44:12 GMT

Fantastic - this DID solve my problem of not being able to debug my ASP.NET app. I had got it set to debug and even tried changing the names etc. with no success.
Checking the IIS setting “Cache ISAPI Applications” as it was NOT selected solved the problem.
A big thankyou to the person who posted that.

Debugger Problem Solved

Thu, 12 Aug 2004 01:48:25 GMT

it is because the proj was not set to debug

Problem with Visual Web Developer 2005

Tue, 27 Jul 2004 04:05:28 GMT

First, I assume you do realize that .NET v2.0 and VWD 2005 are in the first Beta -- so there is no guarantee, nor support, that anything will work with it -- and I'm not just referring to my stuff. OK, having said that, that doesn't mean things won't work, but its important to set the expectations of what a Beta really means -- it is not something that is expected to be routine.

As for the error you're getting, this actually has nothing to do with v2.0 and 2005 -- this is a very common message in ASP.NET apps that result from not setting up the web application in IIS. You should be able to resolve this the same way you do for any other web applications by creating a virtual directory if necessary, and making sure the IIS Application setting is enabled.

Thanks, Paul Wilson

Problem with Visual Web Developer 2005

Mon, 26 Jul 2004 20:46:42 GMT

Hi Wilson,

I download .Net framework 2.0 and Visual Web Developer 2005 from www.microsoft.com
But when I try to use your source code, it has an error.

Server Error in '/WilsonDotNet' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:

Line 21: </appSettings>
Line 22: <system.web>
Line 23: <authentication mode="Forms">
Line 24: <forms name=".WilsonDotNetId" loginUrl="Login/" />
Line 25: </authentication>

Source File: C:\Daniel\WilsonDotNet\_www.wilsondotnet.com\web.config Line: 23

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.40607.16; ASP.NET Version:2.0.40607.16

Debugger Problem Solved

Fri, 19 Mar 2004 08:12:14 GMT

Yes, thanks!

Now I have changed all my subfolder index-files and it works like a charm.

You don't have to change the filenames outside VS. I just changed them in solution explorer. Right click on the aspx-file you want to change the name on and choose rename. Thats it!

It really sucks when you cant debug. It's impossible to work.

Tanks again =)

Malin

Debugger Problem Solved

Fri, 12 Mar 2004 12:28:10 GMT

I just struggled with this for a while, and was able to fix it by manually editing the .vbproj file as follows:

<VisualStudioProject>
<VisualBasic
...
>
<Build>
<Settings
...
>
<Config
Name = "Debug"
...
DebugSymbols = "true"
/>

The DebugSymbols attribute was showing "false" for some reason. Fixing it by hand solved the problem.

Debugger Problem Solved

Mon, 02 Feb 2004 08:07:45 GMT

This is an additional information to solve the debug problem ,
=====
ERROR:
The Breakpoint will not currently be hit. No Symbols have been loaded for this document.

Criteria For Resolution:

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

- Correctly be able to debug ASP.NET Web Applications on your Windows XP machine.

Cause:

======

- In IIS, the “Cache ISAPI Applications” CheckBox was not selected.

Resolution:

========

1) Open up the IIS Management Console (Start -> Run -> Type: inetmgr)

2) Right-click on the Default Web Site Tab and choose Properties.

3) Choose the Home Directory Tab.

4) In the Application Settings section, choose the Configuration Button.

5) Choose the Mappings Tab and ensure that the “Cache ISAPI Applications” checkbox is selected.

Hope this will be helpful to sombody.

HTML View

Wed, 30 Jul 2003 11:23:18 GMT

Meant to say "...and then remove them after."

HTML View

Wed, 30 Jul 2003 07:24:32 GMT

Thanks a ton Paul!

I'm going to add <body></body> tags while developing the page and them removed them after.

I love your Master Pages implementation!

HTML View

Mon, 28 Jul 2003 06:18:49 GMT

Its one of the annoying things about VS.NET that only has one workaround that I know of: add the body tag! I know some people that add it and while they are working and then remove it when done to get the intellisense. I decided to put the html, head, and body tags in each page to enable intellisense and to allow me to set page-specific title and meta-tags. Its not the "optimal" solution I would have hoped for, but its the best we can do until the next version of VS.NET comes out (which totally rocks).

Thanks, Paul Wilson

HTML View

Fri, 25 Jul 2003 08:02:38 GMT

Hello Everyone,

I have purchased the premium code and am currently using the MasterPage.cs server control and a template .ascx user control.

Problem is, when I'm in HTML view of my .aspx pages, I do not get intellisense for any of the ASP.net server controls.

For example, when I type <asp there are no options, or if I add a tag such as <asp:label></asp:label> and try to add properties, I do not receive intellisense.

Here's my .aspx page:

<%@ Page language="c#" Codebehind="test.aspx.cs" AutoEventWireup="false" Inherits="myapp.test" %>
<%@ Register TagPrefix="myapp" Namespace="myapp" Assembly="myapp" %>
<myapp:masterpage id="MasterPage" runat="server">
<myapp:contentregion id="MasterPageTitle" runat="server">
<myapp:pagetitle id="PageTitle1" runat="server" key="test_title" cssclass="pageTitle"></myapp:pagetitle>
</myapp:contentregion>

My content...

</myapp:masterpage>

I've already successfully built the project. And the DESIGN view seems to work just fine.

What am I doing wrong?

Thanks!

Debugger Problem Solved

Thu, 30 Jan 2003 12:04:01 GMT

Debugger Problem Solved

VS.NET's Debugger currently has a bug that causes some very odd behaviors when you have several Pages (or User Controls) with the same name in different folders in your project. A very good example would be the case where every folder has a Page named Default.aspx!

The behavior is that sometimes debugging does not work in at least some of these files, or maybe it works in parts of the files but not in other parts (saying symbols not loaded), or worse is when you set a breakpoint in one file and it randomly jumps to one of the others.

MS says the solution is to not have multiple files of the same name, but what about Default? My workaround is to manually change the names of the code-behind files (and matching resx) to something that is unique -- which then fixes the debugging problem and it all works well.

The problem is that these name changes must be done outside of VS.NET, by changing the file names, the codebehind attribute in the associated Page or User Control, and the Project file. I saw some reason to believe VS.NET will sync the Project file for you, but I do it myself.

While its a pain to do this, and it takes some getting used to, it will solve your problem. You will notice that my Default.aspx pages have their code-behind file named DFolder.aspx.cs, and I also have a ControlMain.ascx in each folder with code-behind named CFolder.ascx.cs.

Thanks, Paul Wilson