Can you please clarify the situation with building/developing .NETv3 apps for the July CTP (in the absence of an matching Orcas release)? I have an XBAP application out there already (for Vista Media Center/JuneCTP – see http://mobilewares.net/mce/bphtm.htm) and want to ensure users can actually run it. (and that I can continue to work on it).
Can an XBAP application (written initially for June CTP/Orcas etc) actually be compiled to work with July CTP? (with or without VS2005)
alternatively –
Can a compiled XBAP application for June CTP be run on July CTP?
If the answer to the above questions are both ‘no’…. Can you please advise on what we are supposed to do in the meantime (and when this situation might be rectified with new CTP’s)..?
thanks
Niall
Yes, a rebuild of your application should run fine on the July CTP. You do not need a new build of Orcas to be able to recompile your XBAP using VS or command line (Orcas provides only the development environment experience, it does not affect compilation or runtime).
With respect to running applications that are compiled for June CTP when you have July CTP installed — I have not tried this, but I expect that it will not work. I believe we had an internal version number change between June and July that would prevent this from working, although I am not completely certain. When I get a chance to try this out for myself, I will let you know. If you get a chance to try it before I do, please report back. :)
Hi –
Thanks for the response…. So in ‘theory’ I should be able to uninstall Orcas (leaving June .NETv3 and Windows SDK’s) – and then recompile it under VS2005. (this is just to test I’m not going to a point of no return with the July CTP’s)…
I’ll also give the existing JuneCTP release of my app a shot on Vista 5472 when it eventually finishes downloading (and test the JuneCTP compiled app running on July CTP question) – and report back if it works…
thanks
Niall
Niall,
You may uninstall Orcas if you wish, but there is no need to. Orcas gives you the app templates for building .Net FX 3.0 apps, and these should work pretty well with the July CTP…
Is there any official source for changes between CTPs. The full setup (runtime, SDK, etc.) is a large download, and just installing is quite time consuming. Hence it would be nice to have a brief idea of what is different between releases. I know in the past people have blogged about the changes, but a more centralised source would be nice.
Oh…. And as for the .Net framework 3.0 – we are really starting to see the power of managed code now!
Andy, there isn’t an official source for changes, but I agree with you that it would be nice to have. I will pass the feedback along to the team. As far as WPF is concerned, there are no major changes between June and July — just a few weeks worth of bug fixes. I am not certain about the other .Net Framework 3.0 components though.
I’m glad you are enjoying the platform! :)
Hi,
just to report back… I installed the Vista July CTP – along with Windows SDK July – and VS2005… I found that initially – I was unable to open my XBAP projects in VS2005 at all (msg was ‘Project Type Not Supported’) – nor was I able to compile it from the command line.
I then installed the Orcas release from June (not the updated one a few days ago) – and was able to build and compile everything as per usual.. This was despite the MSDN notes saying that Orcas would not be installable at all (‘the install will be blocked and will fail’ was the exact words I think)..
The only missing part is that I get a black window where Cider used to run (which is of no issue to me as I normally get the Whoops message anyhow due to using a lot of styles + static references).. The intellisense stuff works a treat still (as do the templates).
Also just to confirm – I was unable to run the app previously compiled with JuneCTP on the July CTP (so as you mentioned I assume its a version change issue)..
Anyhow hope this info is of some use … and now I’m looking forward to a new Orcas release and some updated Expression tools…8)
thanks
Niall
Hi Lauren,
A question about submitting bug reports for WPF. Is the Microsoft Connect site still the correct place for submissions? I’ve just submitted a bug, but the “version” drop-down selection only shows as far as the Feb CTP…
I got the aforementioned “Project Type Not Supported” error, but when I tried to install the Orcas June CTP, it said I didn’t have the .Net 3.0 runtime installed. I looked in the MSI, and it was looking for a product code whereas the July .Net Runtime is installed by name in the registry (it’s looking in the Uninstall reg key). I hacked in the key it was looking for and restarted, and Orcas installed, but none of my WPF projects would load. I tried to recreate the projects, but the June Orcas would create the project but wouldn’t open it (“Project type no supported”).
I’m also getting a weird issue where whenever I launch the WWF extension installer, it jumps into the Windows SDK installer, even if I reinstall it
Oh, yeah, left out a middle step in there where I reverted everything back to June, but my external resourcedictionaries weren’t loading, which led me back to putting a bunch of July stuff back on (trying to eliminate variables). Unfortunately, my system restore points don’t go back far enough, but I’ll probably move over to a clean system in another couple of months.
Hi,
Can you please clarify the situation with building/developing .NETv3 apps for the July CTP (in the absence of an matching Orcas release)? I have an XBAP application out there already (for Vista Media Center/JuneCTP – see http://mobilewares.net/mce/bphtm.htm) and want to ensure users can actually run it. (and that I can continue to work on it).
Can an XBAP application (written initially for June CTP/Orcas etc) actually be compiled to work with July CTP? (with or without VS2005)
alternatively –
Can a compiled XBAP application for June CTP be run on July CTP?
If the answer to the above questions are both ‘no’…. Can you please advise on what we are supposed to do in the meantime (and when this situation might be rectified with new CTP’s)..?
thanks
Niall
Yes, a rebuild of your application should run fine on the July CTP. You do not need a new build of Orcas to be able to recompile your XBAP using VS or command line (Orcas provides only the development environment experience, it does not affect compilation or runtime).
With respect to running applications that are compiled for June CTP when you have July CTP installed — I have not tried this, but I expect that it will not work. I believe we had an internal version number change between June and July that would prevent this from working, although I am not completely certain. When I get a chance to try this out for myself, I will let you know. If you get a chance to try it before I do, please report back. :)
Hi –
Thanks for the response…. So in ‘theory’ I should be able to uninstall Orcas (leaving June .NETv3 and Windows SDK’s) – and then recompile it under VS2005. (this is just to test I’m not going to a point of no return with the July CTP’s)…
I’ll also give the existing JuneCTP release of my app a shot on Vista 5472 when it eventually finishes downloading (and test the JuneCTP compiled app running on July CTP question) – and report back if it works…
thanks
Niall
Niall,
You may uninstall Orcas if you wish, but there is no need to. Orcas gives you the app templates for building .Net FX 3.0 apps, and these should work pretty well with the July CTP…
Is there any official source for changes between CTPs. The full setup (runtime, SDK, etc.) is a large download, and just installing is quite time consuming. Hence it would be nice to have a brief idea of what is different between releases. I know in the past people have blogged about the changes, but a more centralised source would be nice.
Oh…. And as for the .Net framework 3.0 – we are really starting to see the power of managed code now!
Andy, there isn’t an official source for changes, but I agree with you that it would be nice to have. I will pass the feedback along to the team. As far as WPF is concerned, there are no major changes between June and July — just a few weeks worth of bug fixes. I am not certain about the other .Net Framework 3.0 components though.
I’m glad you are enjoying the platform! :)
Hi,
just to report back… I installed the Vista July CTP – along with Windows SDK July – and VS2005… I found that initially – I was unable to open my XBAP projects in VS2005 at all (msg was ‘Project Type Not Supported’) – nor was I able to compile it from the command line.
I then installed the Orcas release from June (not the updated one a few days ago) – and was able to build and compile everything as per usual.. This was despite the MSDN notes saying that Orcas would not be installable at all (‘the install will be blocked and will fail’ was the exact words I think)..
The only missing part is that I get a black window where Cider used to run (which is of no issue to me as I normally get the Whoops message anyhow due to using a lot of styles + static references).. The intellisense stuff works a treat still (as do the templates).
Also just to confirm – I was unable to run the app previously compiled with JuneCTP on the July CTP (so as you mentioned I assume its a version change issue)..
Anyhow hope this info is of some use … and now I’m looking forward to a new Orcas release and some updated Expression tools…8)
thanks
Niall
Hi Lauren,
A question about submitting bug reports for WPF. Is the Microsoft Connect site still the correct place for submissions? I’ve just submitted a bug, but the “version” drop-down selection only shows as far as the Feb CTP…
Andy, please use this site for bug reporting: http://connect.microsoft.com/Main/content/content.aspx?ContentID=2220
I got the aforementioned “Project Type Not Supported” error, but when I tried to install the Orcas June CTP, it said I didn’t have the .Net 3.0 runtime installed. I looked in the MSI, and it was looking for a product code whereas the July .Net Runtime is installed by name in the registry (it’s looking in the Uninstall reg key). I hacked in the key it was looking for and restarted, and Orcas installed, but none of my WPF projects would load. I tried to recreate the projects, but the June Orcas would create the project but wouldn’t open it (“Project type no supported”).
I’m also getting a weird issue where whenever I launch the WWF extension installer, it jumps into the Windows SDK installer, even if I reinstall it
Oh, yeah, left out a middle step in there where I reverted everything back to June, but my external resourcedictionaries weren’t loading, which led me back to putting a bunch of July stuff back on (trying to eliminate variables). Unfortunately, my system restore points don’t go back far enough, but I’ll probably move over to a clean system in another couple of months.