Re: Erroneous Compile Errors
From: Lazarus Lang (lazaruslang_at_yahoo.com)
Date: 04/26/04
- Previous message: David: "Visual Studio.NET Prerequisities"
- In reply to: Robert Pfeffer: "RE: Erroneous Compile Errors"
- Next in thread: Gary Chang: "RE: Erroneous Compile Errors"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 26 Apr 2004 21:57:17 +0200
"Robert Pfeffer" <rmp@svs.com> wrote in message news:8AA31AD7-4E4F-4B22-8DA0-DB37139A119B@microsoft.com...
> The second question first. The errors are in almost every file in all projects in the solution. If I switch to anther
configuration and do a build then all the files compile clean (same files that got errors).
> D:\svs\vsp\TestMaintenance\TestMaintenance.vb(180): 'GroupName' is not a member of 'TestMaintenance.TestMaintenance'.
Just chiming in here. I see the exact same errors at work everyday. Usually happens after half a dozen
(or so) edits have been made to various source files in various projects in our solution. They're always the
same errors ("xxx is not a member of yyy") and they always go away after closing and reopening
visual studio.net and reloading the solution. A real nuisance they are too... :-(
Maybe it's helpful to describe our solution. It contains 42 projects: about 30 winforms forms, some
winforms custom controls, some class libraries and 1 ATL3 COM DLL. The majority
of the forms uses ADO.NET to access the SQLServer DB but the more recent ones use the BLL
class library which in turn uses a ORmapper-generated DAL class library to access the DB. (The
ADO.NET-based winforms will be "ported" to this BLL sooner or later, if and when the need arises).
We're intensively using visual inheritance in order to achieve a consistent look and feel for our forms.
We're also using ComponentOne Studio.NET all over the place for better (looking)
toolbars, menus and grids and for their reports designer.
If I'm not mistaken (but I daren't swear on it) the errors always appear in the ADO.NET-based
projects in the form classes which are generated by the MSDataSetGenerator from the .xsd schema's.
> If I switch the solution configuration to a different one then it builds with no errors.
> If I then switch back to the original solution configuration then it also builds with no errors.
This is something I hadn't tried before. I'll try it tomorrow. Maybe it's faster than closing and reloading
vs.net (and the big solution).
Hoping for a nice reference to a kb article telling us how to avoid this.
But a nice "omg, this will be fixed asap" will do nicely as well. ;-)
HTH
eltwo
- Previous message: David: "Visual Studio.NET Prerequisities"
- In reply to: Robert Pfeffer: "RE: Erroneous Compile Errors"
- Next in thread: Gary Chang: "RE: Erroneous Compile Errors"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
