.NET SDK

[=?ISO-8859-2?Q?=A3ukasz?=]

Hello,

Am I allowed to create comercial applications using .NET Framework SDK?
(or Visual Studio .NET 2003 from MSDN AA?)

Best Regards,
£ukasz

 

[John Timney \(ASP.NET MVP\)]

yes

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

 

[=?ISO-8859-2?Q?=A3ukasz?=]

yes

_*Both*_ in .NET Framework SDK and in VS .NET (from MSDN AA)?

 

[Lloyd Dupont]

yes

 

[Lloyd Dupont]

if you have other question like this one the answer is: yes - yes - yes
with the following exceptions:
- you can't use rotor to build commercial application
- you can't ship the .NET 2 beta 2 in your application (but you can sign
go-live and let the user download them)

 

[Peter van der Goes]

Hello,

Am I allowed to create comercial applications using .NET Framework SDK?
(or Visual Studio .NET 2003 from MSDN AA?)

Best Regards,
£ukasz

As an MSDNAA Administrator, I have to disagree with the other responses in
regard to software acquired through MSDNAA. Specifically, in the MSDNAA
EULA:

"1.5 "Use" shall mean the non-commercial use of the Software by Faculty,
Staff, and/or Students solely to: (a) develop, support, and conduct
educational classes, labs, or related programs offered by Qualified
Educational User which have been approved for participation in the MSDN
Academic Alliance Program and that have the purpose of instructing and/or
training Students to develop and use the Software; (b) conduct
non-commercial research projects utilizing the Software (note: research done
on behalf of the National Science Foundation or the U.S. Government
qualifies as "non-commercial" research); and/or (c) design, develop, test,
and demonstrate software applications or hardware that work in conjunction
with the Software only for the purposes as listed in Section 1.5(a) or
1.5(b). "Use" of any Software under Section 1.5(a) shall be limited to
instructing and training Students to use such Software, any other Software
available under the MSDN Academic Alliance Program, and any software
developed during such class, lab, or related program. "Use" under this
Amendment shall not include the use of the Software for general business
purposes other than by Qualified Educational User's employees engaged in
support and user support of the Software and the management of compliance
with the MSDN Academic Alliance Program. If a Student creates a software
program resulting from the proper Use of the Software consistent with this
Section 1.5, then such Student may commercially use and/or sell such
software program upon the purchase of, and adherence to the terms and
conditions of, a retail license of the applicable Software used to create
such software program."
For the entire EULA, look here:

http://www.msdnaa.net/EULA/NA/English.aspx#amendment

 

[=?ISO-8859-2?Q?=A3ukasz?=]

Hello,

Am I allowed to create comercial applications using .NET Framework SDK?
(or Visual Studio .NET 2003 from MSDN AA?)

Best Regards,
£ukasz

As an MSDNAA Administrator, I have to disagree with the other responses in
regard to software acquired through MSDNAA. Specifically, in the MSDNAA
EULA:

[...]

For the entire EULA, look here:

http://www.msdnaa.net/EULA/NA/English.aspx#amendment

Thanks for your answer. I have 2 more questions:

1) Can I build commercial applications using only .NET Framework SDK?
(even if it's installed with VS .NET (from MSDN AA))

2) Can I create commercial application using VS .NET (from MSDN AA) - I
mean only source code, and then compile it from command prompt using
..NET Framework SDK tools (csc.exe, vbc.exe, ...)?

Best Regards,
£ukasz

 

[John Timney \(ASP.NET MVP\)]

Actually Peter is probably right, but the licencing around the SDK in this
instance is very unclear given its a free download outside of MSDN anyway.
Given that your apps will run in the free .net runtime - not the sdk (or
vs.net) its a questionable debate as it would imply two licence models to
one piece of software. If you use the SDK (outside of MSDN) then its not
going to be an issue.
--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

Hello,

Am I allowed to create comercial applications using .NET Framework SDK?
(or Visual Studio .NET 2003 from MSDN AA?)

Best Regards,
£ukasz

As an MSDNAA Administrator, I have to disagree with the other responses
in regard to software acquired through MSDNAA. Specifically, in the
MSDNAA EULA:
[...]

For the entire EULA, look here:

http://www.msdnaa.net/EULA/NA/English.aspx#amendment

Thanks for your answer. I have 2 more questions:

1) Can I build commercial applications using only .NET Framework SDK?
(even if it's installed with VS .NET (from MSDN AA))

2) Can I create commercial application using VS .NET (from MSDN AA) - I
mean only source code, and then compile it from command prompt using .NET
Framework SDK tools (csc.exe, vbc.exe, ...)?

Best Regards,
£ukasz

 

[Lloyd Dupont]

It's also not very fair and although you could always build the final
release manuall with NAnt, it could be argued in court that you've used
VS.NET all along.
On top of that VS.NET2005 will cost only 300$....

--
If you're in a war, instead of throwing a hand grenade at the enemy, throw
one of those small pumpkins. Maybe it'll make everyone think how stupid war
is, and while they are thinking, you can throw a real grenade at them.
Jack Handey.

Hello,

Am I allowed to create comercial applications using .NET Framework SDK?
(or Visual Studio .NET 2003 from MSDN AA?)

Best Regards,
£ukasz

As an MSDNAA Administrator, I have to disagree with the other responses
in regard to software acquired through MSDNAA. Specifically, in the
MSDNAA EULA:
[...]

For the entire EULA, look here:

http://www.msdnaa.net/EULA/NA/English.aspx#amendment

Thanks for your answer. I have 2 more questions:

1) Can I build commercial applications using only .NET Framework SDK?
(even if it's installed with VS .NET (from MSDN AA))

2) Can I create commercial application using VS .NET (from MSDN AA) - I
mean only source code, and then compile it from command prompt using .NET
Framework SDK tools (csc.exe, vbc.exe, ...)?

Best Regards,
£ukasz

 

[Peter van der Goes]

Thanks for your answer. I have 2 more questions:

1) Can I build commercial applications using only .NET Framework SDK?
(even if it's installed with VS .NET (from MSDN AA))

2) Can I create commercial application using VS .NET (from MSDN AA) - I
mean only source code, and then compile it from command prompt using .NET
Framework SDK tools (csc.exe, vbc.exe, ...)?

Best Regards,
£ukasz

Beyond showing you the MSDNAA EULA and quoting the pertinent part, I'm not
going to try interpretations. I suggest you contact Microsoft by phone and
ask your questions. I am neither a Microsoft employee nor an attorney.

 

[Cor Ligthert [MVP]]

Peter,

Correct, in my opinion is it good to add again that your given answers were
(regarding as you wrote) only about the MSDNAA part of the question.

If you have another idea, please correct me.

Cor

 

[Peter van der Goes]

Peter,

Correct, in my opinion is it good to add again that your given answers
were (regarding as you wrote) only about the MSDNAA part of the question.

If you have another idea, please correct me.

Cor

Absolutely! I was not trying to address the OP's question about the SDK at
all.
I was addressing his Visual Studio .NET acquired through an MSDNAA
membership.
The MSDNAA EULA is quite clear regarding acceptable use of the software.

 

[=?ISO-8859-2?Q?=A3ukasz?=]

If you use the SDK (outside of MSDN) then its not

going to be an issue.

I was not trying to address the OP's question about the SDK at
all.

That is my last question (sorry but my English isn't so good as I'd like
it to be, and now (after such many answers) I'm a little confused):

Using VS .NET I can only make freeware applications, and if I want to
make comercial applications I have to write it manually in e.g. notepad
(not VS .NET) and compile from command prompt with .NET SDK. - Is that
right or not?

Best Regards
£ukasz

 

[John Timney \(ASP.NET MVP\)]

The terms of your licence probably restrict you from using vs.net to create
commercial apps - that could still be a freeware app if its used
commercially. As Peter suggests, phone your local MSDN contact and check
your licence out..

You can use the SDK and notepad.

Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

 

[Morten Wennevik]

Hi Åukasz,

If you have the Academic Edition of Visual Studio.Net, then yes, you are not allowed to make commercial applications or make any kind of profit of what you create with it. For any other edition I don't think you are prohibited to make commercial applications, but you might want to check with microsoft first if you are uncertain.