VSIP Free, Industry Implications!
-
Well, maybe this is not the right place to post this but now VSIP is free :-D. www.vsipdev.com[^] Surely you can not use VSIP sdk with C# builder and this may be one of the reasons why MS is realeasing it free. There are three types of partnership now including a free one. I wasnt a signed up VSIP partner because I did not have 10k to blow, however what are the implications that this changes are going to impact within those that have being developing premium and excelent products such as CodeObject (already VSIP Partner under older subscription)? I know that I keep bringing the same issue but, is this Fair with the existing partners? Cheers ES
-
Well, maybe this is not the right place to post this but now VSIP is free :-D. www.vsipdev.com[^] Surely you can not use VSIP sdk with C# builder and this may be one of the reasons why MS is realeasing it free. There are three types of partnership now including a free one. I wasnt a signed up VSIP partner because I did not have 10k to blow, however what are the implications that this changes are going to impact within those that have being developing premium and excelent products such as CodeObject (already VSIP Partner under older subscription)? I know that I keep bringing the same issue but, is this Fair with the existing partners? Cheers ES
Erick Sgarbi wrote: There are three types of partnership now including a free one. I wasnt a signed up VSIP partner because I did not have 10k to blow, however what are the implications that this changes are going to impact within those that have being developing premium and excelent products such as CodeObject Do not worry, they fall under additional benefits, which is not accessible to the free users. Or you can read the overview of the partner levels here... Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
-
Well, maybe this is not the right place to post this but now VSIP is free :-D. www.vsipdev.com[^] Surely you can not use VSIP sdk with C# builder and this may be one of the reasons why MS is realeasing it free. There are three types of partnership now including a free one. I wasnt a signed up VSIP partner because I did not have 10k to blow, however what are the implications that this changes are going to impact within those that have being developing premium and excelent products such as CodeObject (already VSIP Partner under older subscription)? I know that I keep bringing the same issue but, is this Fair with the existing partners? Cheers ES
Section 2 b from the VSIP EULA : "...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; ..." So MS grants thereby their own right to reject any kind of product, while at the same time they give themselves a good legal tool to know what software companies are developing. Either it's too easy to pass the tests, and everyone will come with the VSIP logo on their website. Or it's too hard, and only a selected premium partners will be granted the VISP logo. Those who pay 3000$ or 10000$. Business as usual, the former is IMHO the more likely... Taking advantage of InternetExplorer to steal user's name and password. Taking advantage of InternetExplorer to steal user's clipboard.
-
Section 2 b from the VSIP EULA : "...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; ..." So MS grants thereby their own right to reject any kind of product, while at the same time they give themselves a good legal tool to know what software companies are developing. Either it's too easy to pass the tests, and everyone will come with the VSIP logo on their website. Or it's too hard, and only a selected premium partners will be granted the VISP logo. Those who pay 3000$ or 10000$. Business as usual, the former is IMHO the more likely... Taking advantage of InternetExplorer to steal user's name and password. Taking advantage of InternetExplorer to steal user's clipboard.
I don't see why MS would reject a package if it added something worthwhile - all the way up to an additional programming language, perhaps - to Visual Studio.NET. The requirements aren't exactly onerous - you can download the 'test suite'[^] (actually manual tests) for yourself. They're really only there to ensure that the IDE isn't going to crash and the basic functions still work. The requirements are far lower than the Hardware Compatiblity Tests that driver writers have to pass in order to get their drivers signed. The benefits and requirements[^] page indicates that Affiliate (no-charge) partners aren't going to be allowed to use the 'Optimized for Microsoft Visual Studio .NET' logo - you have to pay if you want to do this. The license key allows MS to control what gets loaded into the IDE. This is a good thing, IMO - remembering that a VSPackage is an unmanaged COM component.
-
I don't see why MS would reject a package if it added something worthwhile - all the way up to an additional programming language, perhaps - to Visual Studio.NET. The requirements aren't exactly onerous - you can download the 'test suite'[^] (actually manual tests) for yourself. They're really only there to ensure that the IDE isn't going to crash and the basic functions still work. The requirements are far lower than the Hardware Compatiblity Tests that driver writers have to pass in order to get their drivers signed. The benefits and requirements[^] page indicates that Affiliate (no-charge) partners aren't going to be allowed to use the 'Optimized for Microsoft Visual Studio .NET' logo - you have to pay if you want to do this. The license key allows MS to control what gets loaded into the IDE. This is a good thing, IMO - remembering that a VSPackage is an unmanaged COM component.
Mike Dimmick wrote: I don't see why MS would reject a package if it added something worthwhile - all the way up to an additional programming language, perhaps - to Visual Studio.NET. How about developing Java.Net with it?:-O
"Welcome to Arizona!
Drive Nice - We're Armed..."
- Proposed Sign at CA/AZ Border