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.

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

v1.0 #309

Open
8 of 11 tasks
AlexCuse opened this issue Jun 3, 2015 · 7 comments
Open
8 of 11 tasks

v1.0 #309

AlexCuse opened this issue Jun 3, 2015 · 7 comments
Labels

Comments

@AlexCuse
Copy link
Collaborator

AlexCuse commented Jun 3, 2015

@AlexCuse AlexCuse added the v1.0 label Aug 14, 2015
@AlexCuse
Copy link
Collaborator Author

AlexCuse commented Dec 9, 2015

probably may as well go .net 4.5 at this point

@YodasMyDad
Copy link

Is there an ETA for v1?

@AlexCuse
Copy link
Collaborator Author

I'm hoping to have a beta release out after new years. There's a lot of changes coming from 3.5 that I still need to make sense of, but I have some time over the next couple weeks.

@AlexCuse
Copy link
Collaborator Author

I just pushed a beta 1 release to nuget: https://www.nuget.org/packages/SquishIt/1.0.0-beta1

This breaks 3.5 support.

Also adds WebActivator as a reference, which should allow preprocessors to be self-registering and allow the framework assembly to clean up any temp files created when resolving embedded resources.

It also switches the default minifiers from AjaxMin to YUI - this change I might back out, not certain at this point.

It also has a change that I guess I need to push to 0.9.8.1 that will create directories as needed for output files (inheriting from the parent folder permissions). This eliminates the need to create all of your output folders on server prior to deployment.

@Worthaboutapig
Copy link

Do you have anyone to take up #315? I'd be willing to look at it, using both SquishIt and Nancy and trying to get these running on Mono.

@AlexCuse
Copy link
Collaborator Author

I was starting to see that as a 1.1 feature, just because of my lack of experience w/ Nancy @Worthaboutapig. If you want to look at the Nancy side of things I can probably get you the necessary extensibility points this week though. I looked at this when creating the issue and don't think it was too awful. The main question I had was how best to deliver the aspnet specific bits, and whether or not a new nuget package would be necessary (I'd like to avoid that if possible, to minimize disruption)

@Worthaboutapig
Copy link

@AlexCuse I've made some comments on #315, but I'm happy to start as soon as you like.

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

No branches or pull requests

3 participants