• Comments
  • Hey Christin,

    FYI, the MSDN Forum is still labeled as for the 2003 and 2005 products. Should there be a new section for Microsoft Visual Studio Tools for the Microsoft Office system in 2008?

    While I have you on the line, what's the latest on the Full Trust/Partial Trust story?  Full trust was a showstopper for me in the past because I don't own the server. Am I able to deploy applications to an ASP.NET 3.5 site that permits only partial trust?

    Thanks,

    Ken

  • Link is fixed now.  Ken, are you talking about Office full trust or ASP full trust?  You should probably ask your ASP question on their forum.  Office 2007 requires Full Trust for any addins.

    -Christin Boyd, Microsoft

  • And it's where the VSTO2003 blog used to be :). Christin Boyd has posted a welcome message and that's

  • And it's where the VSTO2003 blog used to be :). Christin Boyd has posted a welcome message and that's

  • So is this something we can use or are you just telling us how great you guys are with only a hint of how to build one?

  • There is an interesting post over at blogs.msdn.com

  • PingBack from http://msdnrss.thecoderblogs.com/2008/01/17/the-reports-of-vbas-demise-have-been-greatly-exaggerated/

  • There is an interesting post over at blogs.msdn.com

  • Hi John

    We would like to see More "Videos"/"Web Casts" with real-life sample implementations, on how work-flow can be used.

  • PingBack from http://msdnrss.thecoderblogs.com/2008/01/17/sharepoint-workflow-tools-video-interview-with-john-durant/

  • Wow, I was browsing the MSDN blogs and came across this soapbox video: http://blogs.msdn.com/vsto/archive/2008/01/17/sharepoint-workflow-tools-video-interview-with-john-durant.aspx

  • Explains some of the enhancements in Visual Studio 2008. Can you say debugging? =) Also some talk about

  • Tools Cloning SharePoint List Security (Freeware Security Tool) ( Download ) U2U CAML Query Builder Feature

  • Tools Cloning SharePoint List Security (Freeware Security Tool) ( Download ) U2U CAML Query Builder Feature

  • Since I'm a VSTO developer who writes software for an industry that uses both Macs and Windows, and this is the VSTO blog, this question seems apropos: Why no VSTO for Mac? Obviously because of no .Net Framework for Mac…so, why no .Net Framework for Mac?

    If giant apps like Wine and Mono can make large chunks of win32 and WinForms run on Intel Macs, there's no reason MS can't figure it out. Considering that the "Rotor" shared-source CLI runs on BSD, and that Silverlight 1.1 has the full DLR for Intel Mac, why no full framework port? There's no downside for developers or users...maybe it's because MS can't see an upside for its shareholders? I would LOVE to be able to sell my VSTO add-ins and document customizations to Mac users--and I'd love to stop having to explain why my 'Microsoft Office' programs don't work on 'Microsoft Office' on the Mac. This is a no-brainer for us insiders, but end users don't really care about frameworks and portability politics--esp. Mac users who are used to hearing "it just works".

    I know the Mac platform is the bane of Microsoft's existence when it comes to major app ports, but maybe if you guys would pull together and make a nice portable Winforms and WPF implementation, you can start sharing a lot more core code between major apps ported to different operating systems, and it won't be as painful to suffer through Apple's periodic API/ABI housecleaning cycles...heaven forbid you actually start compiling stuff like Office, IE, and Media Player on top of the CLR so you could leverage some of that tasty VM portability.

Page 1 of 50 (745 items) 12345»