Donal, There is already a CLI tool that Rohit had written. The C# client can also go in there and have a similar hierarchy in the source tree. BTW, have you considered making it Powershell cmdlets instead?
Thanks, Koushik -----Original Message----- From: Donal Lafferty [mailto:donal.laffe...@citrix.com] Sent: Friday, December 14, 2012 5:23 PM To: cloudstack-dev@incubator.apache.org Subject: RE: Adding .NET/C# client to project The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license. The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs. However, I wanted to know in advance how the code was going to fit in with the existing code base. -----Original Message----- From: Prasanna Santhanam [mailto:prasanna.santha...@citrix.com] Sent: 14 December 2012 12:01 AM To: cloudstack-dev@incubator.apache.org Subject: Re: Adding .NET/C# client to project On Fri, Dec 14, 2012 at 05:18:30AM +0530, Donal Lafferty wrote: > Where do client libraries go in the source tree? Does it matter if > they're not written in Java? > > The background is that there's a .NET SDK that can be added to the > project. Architecturally, its similar to AWS' .NET SDK. Now, not all > API calls are covered, but the API calls supported provide a guide > adding additional support. > What .NET library and what license? Is the plan to include the binary to the codebase? -- Prasanna.,
