I got avalon march CTP yesterday. But installation instructions said, it needs to remove all stuff of former version installed before. And this CTP need to install VS2005 Beta 2 before install .NET framework 2.0 Feb CTP. Is this necessary?
And where can I get some information about what's new in this CTP?
-
-
Well this install order worked .. atleast seems so..
Install:
1. XP with SP2
2. VS 2005 February CTP (Or C# Feb CTP Express, however release notes say there is a bug with Wizard if using that)
3. like the WinFX SDK doc says:
Avalon, Indigo and then the WinFX SDK
If you have already installed some older VS 2005 (beta 1, other than February 2005 CTP) I suggest you get a clean XP SP2.
The "uninstall" of these older versions practically does nothing and unless you are a registry guru and know all places VS+NET+MSDN lib has stuff around and want to spend hours finding and deleting stuff left from the "uninstall", and then hoping the new install works.. Well in that same time you can setup clean XP SP2.
Or if you want to go without VS at all, I guess thats possible too. Seems you still need to do the cleaning of previous VS.. or it may end up not working right.
-
Tyler Brown
Bullets change governments far surer than votes.
In order to use the March 2005 CTP Bits, you need to use the CTP versions of Visual Studio 2005, either the Professional version or Express. I don't have the links handy right now as I'm in a rush, so I'll just give a plug for my blog which has all the information you'll need. WinFX Adventures.
Edit: Someone already beat me to it. Oh well, I tried! Also - The Beta 1 version of VS will not work with the March CTP Bits, neither will Beta 2 which is still in the pipe. -
leighsword
LeighSword
androidi wrote:Well this install order worked .. atleast seems so..
Install:
1. XP with SP2
2. VS 2005 February CTP (Or C# Feb CTP Express, however release notes say there is a bug with Wizard if using that)
3. like the WinFX SDK doc says:
Avalon, Indigo and then the WinFX SDK
If you have already installed some older VS 2005 (beta 1, other than February 2005 CTP) I suggest you get a clean XP SP2.
The "uninstall" of these older versions practically does nothing and unless you are a registry guru and know all places VS+NET+MSDN lib has stuff around and want to spend hours finding and deleting stuff left from the "uninstall", and then hoping the new install works.. Well in that same time you can setup clean XP SP2.
Or if you want to go without VS at all, I guess thats possible too. Seems you still need to do the cleaning of previous VS.. or it may end up not working right.
the Registry of windows is an awful idea, it will damn the windows, makes it crash.
-
Tyler Brown
Bullets change governments far surer than votes.
I agree, I don't like the registry one bit, and I hope that Microsoft is moving away from it. With Longhorn there is a push for writing application data to the User Data folder because the majority of programs will be running with restricted permissions and will not be able to store state and preferences in the registry.
-
Thanks for your information, but Sorry, your blog cannot be displayed ;-( Any else links?
-
Tyler Brown
Bullets change governments far surer than votes.
That's odd... keep trying the link. Blogger's been acting a bit slow the past couple of days for some reason.
Here are a few links in case you can't reach it.
Visual Studio Express CTP SKU's
WinFX CTP SDK Documentation
WinFX CTP Bits Release Notes
Longhorn Developer Center
Microsoft WinFX Newsgroups
-
karstenj
Karsten Januszewski
An article just went live on MSDN that outlines new features and changes in the March CTP: http://msdn.microsoft.com/longhorn/?pull=/library/en-us/dnlong/html/avalonmarch2005ctp.asp
-
Sampy
And I come back to you now - at the turn of the tide
RE: Registry woes
If your app targets Windows XP and above, you can use COM components without registration. This is a feature of the OS so you can use it today but VS 2005 makes it really easy to do. Just set the Isolated property to "true" on you COM reference and we'll generate the proper manifest you need to use that object. It works great with ClickOnce and helps you overcome one of the hurdles to using that technology: dependency on old COM stuff.
My team wrote the manifest generating code so I'm a little biased
-
LOL
BTW I am just trying out XAMLPad.. It's great though this "no-compilation" tech should be added to VS too so you'd get the intellisense and formatting at the least
I am not sure is it my system or what, but it always creates a "command prompt" window along with the XAMLPad window.. So I get an useless window wasting space from taskbar. Anyway here is a quick C# snippet to kill this problem.
string winfxbinpath=@"C:\Program Files\Microsoft SDKs\WinFX\bin\"; System.Diagnostics.ProcessStartInfo startInfo = new System.Diagnostics.ProcessStartInfo(winfxbinpath+"XAMLPad.exe"); startInfo.CreateNoWindow = true; startInfo.UseShellExecute = false;
startInfo.WorkingDirectory=winfxbinpath; System.Diagnostics.Process.Start( startInfo ); -
Tom Servo
W-hat?
They changed a lot of stuff in this CTP. For once am I not so pleased that they removed the TextEditor.IsEnabled property on the TextFlow (old TextPanel or variation of it). :/
--edit: And oh, great documentation on the Avalon bits.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.