What I mean is that you do not have to recompile every library when you are only working in one of say 3 or 4. Instead of recompiling and entire project of a larger size you only recompile the one portion you are working on.
Greg -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Stoyan Damov Sent: Friday, July 14, 2006 09:40 To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: Virtual methods in .NET - was Implementing an Interface - C# vs. VB.NET So I should package my code in a less cohesive structure because Microsoft's compiler can't compile faster? Btw, it only gets worse as you add more projects to the solution. I'm stopping now as my blood pressure went too high and I'll start swearing, and I swear very badly (why wouldn't they just implement this "We Share Your Pain" program! :) Cheers, Stoyan On 7/14/06, Gregory Miley <[EMAIL PROTECTED]> wrote: > I don't find that it takes to long to build a project. However, if you > project is massive enough to cause a horrible slow down in the build process, > perhaps it would be better to break your project out into several projects > within the same solution and libraries? > > Greg > > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Eyvind > Axelsen > Sent: Friday, July 14, 2006 04:34 > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Subject: Re: Virtual methods in .NET - was Implementing an Interface - > C# vs. VB.NET > > Staying OT, I am also experiencing loads of crashes in VS. Daily. I have no > betas installed, but still it continues to crash. The WinForms designer is > especially bad, and I have to use it a lot. I am wondering how they could > ever let that beast out of the door. Furthermore, I am experiencing the same > kind of problems that Stoyan describes, VS just suddenly disappears, vanishes > into thin air. And if that wasn't enough, it takes way too long to open the > WinForms designer, seemingly because it rebuilds the toolbox or something > along that line. And it takes forever to build a large project. I must say > that I am very disappointed that we have not yet seen an SP. > > Eyvind. > > -----Opprinnelig melding----- > Fra: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] På vegne av Shawn > Wildermuth > Sendt: 14. juli 2006 01:42 > Til: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > Emne: Re: [ADVANCED-DOTNET] Virtual methods in .NET - was Implementing > an Interface - C# vs. VB.NET > > Stoyan, > > This is off-topic a bit, but I have to say I use VS 2005 5-6 hours a day > since release (and before), and I have not seen what you are seeing. Do you > have WinFX (.NET 3.0) installed or did you have the Beta installed before it? > I am just curious...also, any chance any add-ins are doing it? > > > Thanks, > > Shawn Wildermuth > Wildermuth Consulting Services, LLC > http://adoguy.com > C# MVP, MCSD.NET, Author and Speaker > > > > -----Original Message----- > > From: Discussion of advanced .NET topics. > > [mailto:[EMAIL PROTECTED] On Behalf Of Stoyan > > Damov > > Sent: Thursday, July 13, 2006 7:35 PM > > To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM > > Subject: Re: [ADVANCED-DOTNET] Virtual methods in .NET - was > > Implementing an Interface - C# vs. VB.NET > > > > On 7/13/06, J. Merrill <[EMAIL PROTECTED]> wrote: > > > Are you annoyed that they used different keywords > > (Overridable vs Virtual, NotOverridable vs Sealed), or are you > > annoyed at the default they chose for VB.Net (when overriding a > > virtual method, it defaults to the method being virtual, while > > declaring a new method defaults to Sealed)? > > > > > > It's true that they might have chosen the same keywords > > that C# has, given that it's a new language with new concepts; but > > one could argue that they chose "more meaningful" or "more English-like" > > or "less computer-sciencey" names for VB.Net because of the "less > > geeky" nature of many old-VB programmers. > > > > > > At 10:51 AM 7/8/2006, Stoyan Damov wrote > > > >[ranting] > > ... > > > > Actually I don't know what am I annoyed at :) I could care less > > about VB.NET. I guess I was just tired and grumpy the night I posted > > this :) But hey, there's always a reason to yell at Microsoft! :) > > For example, my VS 2005 simply disappeared (sliently crashed) > > several times today as I was typing code (disappearing while using > > the Windows Forms designer is something I can live with). I guess it > > happened because it was 13th. Those fucks! :) Where's my SP1? ;( > > > > Cheers, > > Stoyan > > > > =================================== > > This list is hosted by DevelopMentorR http://www.develop.com > > > > View archives and manage your subscription(s) at > > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > -- Cheers, Stoyan =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
