Announcing the Cider November CTP for .Net Framework 3.0 RTM
The November Community Technology Preview (CTP) of the Cider Visual Designer for Windows Presentation Foundation is now available!
As usual Cider is being released as part of the Visual Studio 2005 Extensions for .Net Framework 3.0. This CTP is compatible with the RTM release of .Net Framework 3.0.
There are no new Cider features in this CTP. It is merely a refresh of our September CTP bits to make them compatible with the RTM release of .Net Framework 3.0. The Cider feature set is identical to the feature set we released in September.
Release notes and installation information for the November CTP are published on the Cider Wiki.
The full set of November CTP features can be found in our November CTP Release Notes.
We’ve worked hard to ensure that the capabilities in this CTP will provide you with a good experience for trying out WPF application development in Visual Studio. So we’re really interested in your feedback. Don’t hesitate to ask questions or post comments.
This November CTP is the last planned release of Cider as an extension to Visual Studio 2005. Future CTPs of Cider will be available in the preview releases of the next full version of Visual Studio which is currently code named "Orcas". Check out the Cider Wiki for more details regarding the end of our VS 2005 based CTPs.
The Cider Team
All Replies
You know, thats terrific, but....what are you guys thinking??
There is a release version of .net 3.0 available and the only graphical tools available for it are beta?!?!
and now your saying thats it until "Orcas" is released, and the date for that is well....unknown.
You do expect people to develop applications for Vista don't you? You are planning on .net 3.0 actually being a success? Because to be honest, with the quality of what has been made available so far...it would be really hard to get that impression.
Would you kindly get your act together and release a comercial grade version of cider for Visual Studio 2005 ASAP so the rest of us can develop the next generation of applications that will make Vista a real success.
Adam, thank you for your feedback. I will pass it on
mark
I would like to add that all of the pieces that you need are really ungainly.
You need the framework, you need the templates and now there is cider contained in the Extension and need the windows SDK. This work needs to be integrated into a single msi.
Between VS2005, it's SP1 and all the extensions that comes to more than 10 gigabytes of disk and about 6 different installation to produce a program with the v3.0 CLR.
- I agree with you partially but don't flame them for it. Seriously man don't kill the messenger. But I do agree with you, the product does seem to be falling behind. I look forward to the final release of Cider and the other WPF extensions for VS.
Me too!
I'm really looking forward for a real RTM release of Cider for VS 2005, not just to be included in Orcas. By then, I have to wait longer for Orcas which is still unlnown and it's still scheduled to be released in 2007. Please make a real RTM of Cider for VS 2005 and also please fix the integration bugs with MS Expression Interactive Designer, since I still get errors from the generated XAML from Expression.
I hope the Dev team will respond to this.
Eriawan K.
its not so much a flame as an expression of sheer frustration...
Working with pre-release stuff when you have plenty of time and your just learning is fun and I'll grant you the Cider team has been great up until now with getting releases out regularly during the pre-release period to give us a taste of whats to come. However with the release of .net 3.0 all thats changed.
We are no longer talking about a pre-release product, we are talking about a complete failure on Microsoft’s part to provide a release version of their flagship development environment that supports the release of .net 3.0.
However you know, I'd settle for a pre-release version in which the missing property sheets and event generators just worked. Its being denied even that possibility and told that rather then use 1 piece of pre-release software to develop with, we will need to replace our entire development suite with a pre-release version, that is really poor.
Would it really hurt the schedule that much to issue a RTM or at least 1 more CTP for VS 2005?
I understand your frustration and apologize that we won't be able to release additional CTPs for VS 2005.
Would it really hurt the schedule that much to issue a RTM or at least 1 more CTP for VS 2005?
One of the major pieces of work we needed to do (and one of the major remaining XAML load limitations) was to reliably and robustly support project to project and assembly references. This required changes in VS to support how we do this. This was a large and complex work item that we could not delay any longer. It means that we have a dependency on VS Orcas and cannot run on top of VS 2005 any longer. This means we cannot release additional CTPs that target VS 2005.
mark
