Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ripple 3 should not force you to convert to the ObjectBlocks style config #269

Open
jeremydmiller opened this issue Feb 13, 2014 · 2 comments
Open

Ripple 3 should not force you to convert to the ObjectBlocks style config #269

jeremydmiller opened this issue Feb 13, 2014 · 2 comments

Comments

@jeremydmiller
Copy link
Contributor

As it is, ripple 3 cannot be used in parallel with ripple 2* solutions. Let's introduce a new storage to write the old Xml file format and make conversion be explicit.
@jeremydmiller
Copy link
Contributor Author

Meh, looking like way too much work, so it's going to be a big bang upgrade across the entire world.

@jeremydmiller
Copy link
Contributor Author

Okay, back to we need this. I think we can do this w/o too much effort. I say we re-introduce a DTO for the Solution that is easy to serialize and make INugetStorage switch. I found some other issues while trying to use Ripple 3 against the FubuCore and FubuMVC codebase today we need to address

@jeremydmiller jeremydmiller reopened this Feb 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremydmiller