Cristian, Most of my posts have been me (maybe over-)sharing my discovery process getting the TeamCity BuildAgent going... Things are much more clear <sic> now.
My comments about the registry keys (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP) is that this is usually where one looks, if you're not doing a WMI query, to find out which version of the framework a machine has installed. And since presumably you can't run a 4.5 app on a 4.0-only machine, this _will_ matter. -rb On Sun, Jul 29, 2012 at 6:41 PM, Cristian Prieto <[email protected]>wrote: > Richard, > > Basically you need the 'new' framework if you are using the new libs > included with it or developing libs that support the damn Metro profile. In > "practice" there is no such thing as Framework 4.5, the current 4.5 version > is 4.0.30319.17626 (yes, from the point of view of just versioning the new > framework is just a 'minor revision' of the previous one). > > When you install 4.5 the tools (like msbuild) will be in the same > directory than 4.0 but msbuild (for example) would be using the new > version... check msbuild after installing the 4.5 and you will see that > msbuild engine version is 4.0.30319.17626 (so, it's running 4.5) > > You can make your app run in 4.0 even when you have 4.5 installed, it will > be matter of specify that explicitly in the app.config file. > > I know, that sucks. > > Hope this help, > > Cristian Prieto > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
