What's the release date for NetAdvantage for .NET 2008 Volume 1?

We're currently evaluating 2007.3 with VS2008 and are having terrible problems with the design surface for several of the controls.  So far, Ribbon and tabs.

Thanks 

Hmm.  That doesn't really narrow it down then does it?  Unfortunately, "Q1 of 2008" is too vauge for me to go back to my client and have them sink money into the controls.  We're on a tight schedule as it is, so I'm going to have to start looking at competitors.  Orcas has been in beta for a long time now - why the delay?

And I'm sort of puzzled by the repeated comments I'm seeing about having to contact your dev support team about problems with VS 2008 + 7.3.  I found some of them almost immediately, probably within about 10 minutes of putting a Ribbon onto a surface.  I would think that your internal Q.A. would be able to find the list of bugs pretty rapidly.  And I really don't have any interest (or time) in paying for a product and then doing your Q.A. for you...  Maybe if I were using a free beta, but not a released product.

Vulgrin,

I too am very disappointed at how Infragistics has dropped the ball on the VS2008 RTM release. I sincerely hope they can bring a fully compatible release of their controls to market very quickly.

 -Thad

I guess I have been lucky so far. I have been creating a new project in 2008 and using the 2007 V3 controls in it and haven't run into any problems that I couldn't deal with such as changes being made to a WebGrid not being saved when closing out of quick design mode. Which controls have you had the most trouble with so I'll know what to avoid?

Also, if you wouldn't mind drop me an email to zjones at arinc dot com after you've done your review of the other control tool sets. I would be interested to know what you end up going with. I'll be honest and say I have been reading more about DevExpress suite of tools. I am a HUGE fan of CodeRush and Refactor! Pro.

I agree that, if you have a bunch of established projects, then upgrading all the time would be an issue.  But in my case I have a client that is having us build a new version of an application, and we're using the latest technology release of the .NET platform, including VS.Net because we don't want to START from behind and have to upgrade later.

I also completely agree that I want it to be thoroughly tested - BUT, that doesn't meant that it shouldn't have been by now, or that I want to be the ones doing the Q.A. for them.  Let's be clear, these are not little bugs that happen only in very special circumstances.  The ones I've run into are the equivalent of having to turn the car off and back on while driving 55 on the highway every half-hour or so.

But, no matter, we're looking at other control suites now.  To each their own. 

I'm going to predict a release prior to March 31st :).

It's amazing to me that you guys have customers that even know that a new version of Visual Studio is out. My customers give me the deer-in-the-headlights look anytime I mention Visual Studio or the .Net framework. In Infragistics' defense they have stated in the past that they have been working with the beta versions of 2008 but I'm certain every vendor, even those that have already released 2008 upgrades made sure to test everything with the release version of 2008 before releasing the update. Personally I'd rather see a later release of the 2008 upgrade that has been thoroughly tested than I would one that has been rushed to market just because VS 2008 is out. I rarely install the hotfixes so if something is broken in a volume release it remains broken until the next volume release. There are exceptions, of course, but when you have 50+ web sites that all rely on Infragistics controls it's a royal PITA to upgrade them all at one shot.

The way I see it we have developers have two choices, jump ship or wait. In our case we're waiting.