Ian Ellison-Taylor

aL_ wrote:



i have one question though, where exactly do you post feedback? the msdn forums are vast and im always feeling im posting in the wrong place is there a prefered place there? or is connect the way to go? i havent found a connect project for .net or wpf as a whole (if there is one please link )

General feedback here is just fine. For more specific feedback on VS you can use http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=2136&SiteID=1 or for WPF specifically just use the regular WPF forum http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=119&SiteID=1 and maybe put "SP1" somewhere in the title.

For connect, we come under the general "Visual Studio and .Net Framework" at http://connect.microsoft.com/VisualStudio


Thanks,

Ian.

Ion Todirel wrote:

is it safe to install VS 2008 SP1 Beta on a development machine? I mean we all know Visual Studio is a very heavy piece of software, I don't want to remove the whole thing just to remove SP1

I'd be a little carefull with any beta software and I know some folks have had issues uninstalling. For me, it's worked just fine so it might for you too but I always recommend a VPC, or a complete backup just in case!

Ian.

figuerres wrote:


I understand the issues,

Please If we can get more info on what it can/can't do etc...

for example can we setup a "reboot" / "runOnce" to do that perhaps?

I'm not entirely sure, let me check and get back to you. Around here we do distribute admin-level software using SMS to machines that are locked-down so I know it's possible but I don't know how it works!

Ian.

figuerres wrote:



Can a non-admin user who does not have full access but has a .net 2.0 app today get an update that will boot-strap to .net 3.5 and then get the app w/o an admin logon??

Unfortunately not. This update at least makes some core changes and so requires admin privs. We definitely get this request *a lot* though and it is something we're moving towards (it's just really hard to engineer).

Sorry,

Ian.

The big issues was that we wanted to make some core performance improvements so we couldn't do just a pure feature pack. We could have separated the fixes from the features but got feedback from ISVs early on that it was better to just put them together in to a single release.

I do appreciate the confusion though so this is definitely something we'll re-think for future versions. Do other folks agree we should keep things separate in the future?

Thanks,

Ian.

Ah, good point - we should be clearer about what we're talking about here.  v1 of WPF shipped first as part of .Net 3.0 (and included in Vista), our next version was in .Net 3.5 and what we're talking about here is our 3rd release as part of .Net 3.5 SP1.

Sorry for the confusion,

Ian.

Kam VedBrat (http://blogs.msdn.com/kamvedbrat/default.aspx) has blogged a fair bit about high-DPI support in Windows. For those that don't know Kam he was instrumental behind the high-DPI support for both WPF and Win32 apps.

For the Win32 side of things I'd recommend an article he linked to a while back (http://www.rw-designer.com/DPI-aware) that covers a great number of the common app issues.

Ian.

Intrepid, yes, I grew up near Manchester in England and then moved out to the US about 17 years ago. Yes, I have a weird accent as a result

Ian.

RHM: Well I hope I didn't give that impression because that certainly wasn't my intent! WPF/e is going to be very important to the platform of course but so is WPF. We've already done some "add-ons" for things we didn't quite get to in v1 and we've got a lot more coming!

WPF/e and WPF represent two ends of the spectrum for developers and designers trying to build rich, interactive user experiences. WPF/e is targetted at reach\web end of the spectrum with Ajax\Atlas, DHTML etc. WPF is at the "high end" with deep support for things like flow documents (ala Times Reader), 3D (ala the British Library) and more. Behind both is the same XAML markup and that's really the common thread that ties them together.

Does this help explain things? If not, I'll keep trying There are a lot of connected components (I didn't even mention XPS!) and clearly we need to get better at explaining the continuum.

Thanks for the feedback,

Ian.