Visual Studio SDK Tech Preview Now Available

Visual Studio SDK Tech Preview Now Available

• mikecmr

  *taps foot and waits patiently*
  
  

• George Stein

  ^bump^
  please respond i have a project that i want to release to the public.
  
  

• Munjal Patel

  Just to keep this topic up to date -- I am loathe to leave people out of the loop -- here's a sample copy of what I e-mailed:
  
  

  >>I would appreciate if you could email me the exact phrases of the EULA that you're concerned about. The EULA that you're seeing is the VS 2003 VSIP EULA and will likely be the VS >>2005 VSIP EULA. The more we understand your concerns the easier it will be to address these. My email is weber@[NOSPAM]microsoft.com. Sorry for the late reply: I was on vacation, sans internet access, for awhile. For the record, this EULA (http://www.vsipdev.com/downloads/vsnextgensdk.aspx), labeled "Visual Studio Industry Partner Distribution Agreement" is the major point of contention: all of it. I will be bare-knuckles honest with you: I'm a hobbyist developer. No big money, no corporate sponsorship, no development team. I am (was ) developing a language service package for the 'Boo' language (http://boo.codehaus.org) that I ramble about here (http://geekninja.blogspot.com). The demands are, for a hobbyist developer, ludracris. Given that the beta 2 refresh had no such distribution EULA associated with its download or embedded in the installer (and still does not) I already began working on the VS2005 package, under an acceptable open-source license, located at the Novell Forge (http://forge.novell.com/modules/xfmod/project/ boopackage). However, according to the new (technically old, but I never had to agree to it to get the VS2005 SDK, so new to me) distribution EULA, I won't be able to develop this package anymore. Frankly, I'm just not interested in 'doing it all by myself' and having to maintain it to the end of time, or having to deal with the issue of, 'if something happens to me, what happens to this VS2005 package source ' I dont *want* to deal with all these issues; I'm just not that interested, dig it The only motivating factor is that I want Boo integration in Visual Studio. That's it. The EULA bundled with the installer (and the *ONLY* one I had to agree to, through the sign-up/download/install process) was run-of-the-mill acceptable, but this one I simply cannot handle. Even if the package could not be open-sourced, there are still too many ridiculious requirements: "You shall ensure the quality of reproduced Licensed Software is equivalent to the quality of the Licensed Software as provided by Us. We shall be entitled to periodically, upon reasonable notice, inspect the quality of Your reproduction. Should we be dissatisfied with the quality, We shall notify You in writing and You shall promptly correct such deficiencies;" Are you serious That immediately puts anyone that doesn't have a development team with serious fundage out of the running. "You shall not expose or enable others to expose the functionality contained in the Integration Code in a manner that allows it to be accessed or used by any third party product. By way of example but not limitation, You may not disclose the Integration Code to third parties in source code form;" How are developers supposed to foster a  development community when we can't even share code-snippets ! I am not too keen on having to depend on you guys for code samples that often. "Your Eligible Products must pass the test suite (manual test scripts) that will be provided to You via the VSIP-SDK and You must submit complete and accurate test results to Us. You will receive a license key from Us for each successfully tested Eligible Product. Distribution of Your Eligible Product requires Your rightful receipt from Us of a license key allocated to You;" Yea---... no. There's no need to go through the rest of the bulletin points.

  
  

• Hery Susanto WR

  I wish I could say more, but at this point "we're working on it" is the only thing I can offer.  Seriously, we hear you.  We're working on getting the language to work for everyone involved, but old license is what we have until new language is agreed upon.
  
  Thanks for the feedback.  Keep it coming.
  
  Allen
  
  

• BReisch

  Oh, naughty naughty!
  
  The link to the download offers up the old EULA - the one that explicitly denies use of open source code.
  
  Hence, I cannot download and install the tech preview, since the current EULA for the VS2005 SDK (beta 2 refresh ) does not forbid open source packages. Plus this old EULA has a myriad of fairly stupid restrictions, open source not withstanding.
  
  What's up with that
  
  

• Jason Nowicki

  Some Random Fellah,
  
  I would appreciate if you could email me the exact phrases of the EULA that you're concerned about. The EULA that you're seeing is the VS 2003 VSIP EULA and will likely be the VS 2005 VSIP EULA. The more we understand your concerns the easier it will be to address these. My email is weber@[NOSPAM]microsoft.com.
  
  Thanks - Jason
  

• cakewho

  I too would also like clarification, and would request a looser agreement. As a .Net developer, although there are quirks Visual Studio is the currently the only IDE worth using. While VS2005 definitely is an improvement, there are still some features left untouched. I recently took it upon myself to create a addin that would supply these features to make my life easier and make me more productive. But like Arron ('some random fella') i do not the resources to fully support and code the whole project and would like to release it as open source. Its a great step forward that the VSIP sdk was released to the public for free, but this license agreement is a real shame.
  
  its times like these i wish i was a java developer. using eclispe.
  
  -john
  
• Visual Studio SDK Tech Preview Now Available