Skip to content
This repository has been archived by the owner on May 25, 2021. It is now read-only.

Give ability to dual compile with .NET 4.0 and 4.5 #37

Open
nberardi opened this issue Jun 6, 2012 · 2 comments
Open

Give ability to dual compile with .NET 4.0 and 4.5 #37

nberardi opened this issue Jun 6, 2012 · 2 comments
Assignees

Comments

@nberardi
Copy link
Contributor

nberardi commented Jun 6, 2012

No description provided.

@dlbromen
Copy link
Contributor

Do you have any specific thoughts on what you're looking for or how you want it done? Just another VS2012 solution file or are you looking for something like separate NuGet packages to be produced out of a single build?

@nberardi
Copy link
Contributor Author

Here are the general rules for how I would like the programming to be done.

  • FluentCassandra.csproj is always on the latest and greatest framework
  • When you add features specific to the new framework you wrap it in NET_XX precompiler (ex. .NET 4.5 is NET_45)
  • FluentCassandra should always at least support the current framework and the previous framework

Here is how I think the dual compile should work.

  • A new project is created for .NET 4.0 called FluentCassandra.Net40.csproj
  • The current FluentCassandra project is updated to .NET 4.5
  • The build process will be based out of a command file called build.cmd (I already started the basics of this https://github.com/managedfusion/fluentcassandra/blob/master/build.cmd) and it will build all the supported frameworks, which should just be building the solution like it does now.
  • The build will move the files to a directory specifically structured to create a NuGet package that targets all the supported frameworks.

I am looking for a discussion on the best way to accomplish this or any problems you see with the above approach. The above approach seems to work really well for RestSharp.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants