Peter Bromberg

A number of MVP's have discussed this. Jeffrey Richter wrote an article about it last November. Why make people download a 53MB install in order just to get the CCR.Core and related assemblies

Thanks!




Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

George Chrysanthakopoulos

we have heard this feedback many times indeed. While we do definately see alot of interest in the CCR from non robotics users, currently our team can only afford the non-trivial release management process MSFT requires, for one product/SDK. Other than the size of the download however, which i do agree is alot for a 200k lib, the CCR can be used in any application you want, with no burden or requirements on anything else in MSRS (it was and will continue to be developed as a seperate, independent component).

Another thing to note ofcourse, given its current packaging, is that the CCR is not free for commercial use. Its cost per deployment is about

2$ (our commercial license gives you 200 runtimes for 399$ for a single dev license)

thanx

g





Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

Jon Skeet

Consider this more of the same feedback Smile

It does seem very odd, both that one would have to pay for such a library (when it's a component in the same way that so many other parts of the .NET framework are) and that MS wouldn't release it separately.

I quite understand that your project team may not have the appropriate resources, but please could you pass these suggestions on to the CCR development team, or anyone else who might be able to actually make this cool technology available without baggage or cost

Jon Skeet






Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

George Chrysanthakopoulos

Hi Jon, thank you for the feedback. I developed the CCR, so you are getting through right to the source Smile We will definately keep in mind this feedback as we scale out the use of CCR/DSS across other software domains.



Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

Ian Thomas

This is a "When did you stop beating your wife" type of response (and, I'm not entirely serious of course).

Maybe George and Henrik are getting too much stick from the CLR Teams - ie, "Not Invented Here" syndrome.





Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

Anthony Tarlano

++ for a nice separation




Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

Anthony Tarlano

if you need DDS and CCR launch vehicle why not use Windows Vista SP1




Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

Peter Bromberg

Not sure I understand this one. IMHO people aren't concerned about a launch vehicle, what they are looking for is the CCR assemblies to be made available outside of the Robotics Studio download and licensing arrangement. Do you know something hat we don't know about




Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

George Chrysanthakopoulos

Hi, the licensing of MSRS applies to CCR and it allows you to just take out the CCR assemblies and re distribute them (we have a runtime distribution and licensing clause). For commercial uses, as i have mentioned before, this comes out to about 2$ per runtime distribution.

sorry if the above is a repeat, but until the CCR is indeed packaged on its own, we need to clarify that the current MSRS license allows you to use the CCR independently.

thanx

g





Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

James Chaldecott

I know this is all going over (and over) old ground, but is there any particular reason why "ship vehicle" == "license" #

Couldn't the MSRS license say :

Blah, blah
$399 == 200 redist licenses
Blah, blah

Except for "CCR.Core.dll" which can be redistributed for free.

Is it just a (legal dept) resources thing




Re: Microsoft Robotics - Concurrency and Coordination Runtime (CCR) Suggestion: Break out the CCR and make available on it's own

George Chrysanthakopoulos

thats actually complicated to do the way our group and licensing is setup. So yes, i would say legal reasons make us have a single setup covered by one commercial license