[ 
https://issues.apache.org/jira/browse/QPID-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732377#action_12732377
 ] 

Julien Lavigne du Cadet commented on QPID-1987:
-----------------------------------------------

As long as no .Net 3/.Net 3.5 features are used it should be trivial to either 
compile under VS 2008 or VS 2005. Please note that you would have to recreate a 
solution file for VS 2005 as the one in the sources is for 2008 only (solutions 
files are not compatible between 2005 and 2008).

However, I've been working on the API with VS 2008 and I never had any specific 
problems so far. What kind of errors are you seeing?
It's probably a silly question bug have you regenerated the files from the 
client-010/gentool directory? This is a required step as I changed the the .py 
and .tpl files to accomodate the usual .Net convention regarding method naming 
(in pascal case and not in camel case)

> Patch for 0.10 C# API
> ---------------------
>
>                 Key: QPID-1987
>                 URL: https://issues.apache.org/jira/browse/QPID-1987
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Dot Net Client
>            Reporter: Julien Lavigne du Cadet
>            Assignee: Ted Ross
>            Priority: Critical
>         Attachments: qpid-.net.patch
>
>
> Please find attached a patch correcting the following issues : 
> - Fixes UUID.randomUUID() which is not thread-safe (QPID-1972)
> - Fixes public API to match standard .NET conventions (QPID-500)
> - Fixes code generation to match standard .NET conventions
> - Fixes ToString() methods that don't override base classes
> - Fixes blocking TearingDown in unit tests
> - Use a .config file for tests/samples 
> - Adds interface to Invoker, Session and ClientSession to allow easy mocking 
> of the API
> - Make the console solution compiling under Visual Studio 2008
> I'm more than happy to discuss any of this by email or through JIRA. Please 
> let me know if there's no plan (or nobody available) to evaluate this patch 
> for inclusion. If that is the case, I will consider forking the API to 
> continue fixing the API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Reply via email to