First off, I want to echo the sentiment that others have shown you for this package. Thank you very much for putting this together. Now on to the issue at hand.
I have installed Optimus.Core, Optimus.Providers.Sass and Optimus.Providers.CoffeeScript on Umbraco 6.1.2. I mainly was interested in this package because I am attempting to learn SASS and I was overjoyed to discover this package was available. Upon creating my first .scss file, putting some information into it and hitting save, I get this error:
Could not load file or assembly 'System.Web.Optimization, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
I looked into the web.config to find that the System.Web.Optimization assembly had been referenced but that the version number was 1.1.0.0. I left the old version at that number and set the new version at 1.0.0.0 thinking that I could redirect it, but that didn't work. It still won't let me compile the .scss sheet.
I have one more question after getting this one answered: Where does the compiled stylesheet go? Does it go into the css folder in the root folder?
Thank you for your attention to this, but that didn't fix the issue. I am thinking that it might be something from the System.Web.Optimization call in the Assemblies.
I have no expertise at all in fixing "DLL-Hell", but seeing a redirect from anything between 0.0.0.0 to 1.1.0.0 onto 1.0.0.0 makes my alarm clocks ring... in other words: the newVersion is within the range of those listed in oldVersion, which I can't see as something that would work, right? Is that usually possible?
You are right Chriztian! It is "DLL-Hell"! I had the newVersion set to its default 1.1.0.0 but it did not work with that setting. There was another forum post (and you will have to forgive me for not being able to find it again) that said that the newVersion setting is a redirect and can be used to push in the proper version. I was skeptical and for good reason. So I was trying to use the newVersion parameter to fulfull that.
Any further ideas? I would love to be able to use this package.
I have another quick question about this package. Do you need to be running Umbraco in MVC mode to use it? I created a bundle and received an error about the bundle call. I was looking at the tutorial videos and they were done using an instance of Umbraco that was running in MVC mode. I am currently using Umbraco in webforms mode.
Thanks for responding Tim. I hope that you are doing well and thank you for creating this package.
I have another question: You know how you can create partials, a .scss file that has an "_" in front of the name (ex: _colors.scss) and it will not compile. That way, you don't have all of your files compiling, just the main one. Does that still work for this package?
You might want to work on the compiling feature a little. I am trying to compile my stylesheets, and have Foundation 4 (the minimalized version) in there. It is taking a LONG time to compile. I have been waiting on it for the last 45 minutes.
I see what you are talking about now Tim. When I was having problems with the package early on, several suggestions were to comment out a part of the web.config file. So I simply just uncommented the part and I am good to go. Here is the part that I am referring to:
Error Compiling Dynamic Stylesheet
First off, I want to echo the sentiment that others have shown you for this package. Thank you very much for putting this together. Now on to the issue at hand.
I have installed Optimus.Core, Optimus.Providers.Sass and Optimus.Providers.CoffeeScript on Umbraco 6.1.2. I mainly was interested in this package because I am attempting to learn SASS and I was overjoyed to discover this package was available. Upon creating my first .scss file, putting some information into it and hitting save, I get this error:
I looked into the web.config to find that the System.Web.Optimization assembly had been referenced but that the version number was 1.1.0.0. I left the old version at that number and set the new version at 1.0.0.0 thinking that I could redirect it, but that didn't work. It still won't let me compile the .scss sheet.
I have one more question after getting this one answered: Where does the compiled stylesheet go? Does it go into the css folder in the root folder?
Thanks for help ahead of time!
Brad
I would also love to know how you can bring in other frameworks such as Compass and ZURB-Foundation.
We were able to solve this by commenting out the following lines of code in the web.config file in the root:
Try that?
Thank you for your attention to this, but that didn't fix the issue. I am thinking that it might be something from the System.Web.Optimization call in the Assemblies.
Like I said, I changed it to 1.0.0.0 in the newVersion call to possibly remedy the situation, but that didn't help either.
Hi Brad,
I have no expertise at all in fixing "DLL-Hell", but seeing a redirect from anything between 0.0.0.0 to 1.1.0.0 onto 1.0.0.0 makes my alarm clocks ring... in other words: the newVersion is within the range of those listed in oldVersion, which I can't see as something that would work, right? Is that usually possible?
/Chriztian
You are right Chriztian! It is "DLL-Hell"! I had the newVersion set to its default 1.1.0.0 but it did not work with that setting. There was another forum post (and you will have to forgive me for not being able to find it again) that said that the newVersion setting is a redirect and can be used to push in the proper version. I was skeptical and for good reason. So I was trying to use the newVersion parameter to fulfull that.
Any further ideas? I would love to be able to use this package.
I have another quick question about this package. Do you need to be running Umbraco in MVC mode to use it? I created a bundle and received an error about the bundle call. I was looking at the tutorial videos and they were done using an instance of Umbraco that was running in MVC mode. I am currently using Umbraco in webforms mode.
Like it says on the project page after install you'll need to
Look for
And you don't need to be running in MVC mode it also works in Webforms mode
And the compiled stylesheet will go in the /css dir :)
Thanks for responding Tim. I hope that you are doing well and thank you for creating this package.
I have another question: You know how you can create partials, a .scss file that has an "_" in front of the name (ex: _colors.scss) and it will not compile. That way, you don't have all of your files compiling, just the main one. Does that still work for this package?
You might want to work on the compiling feature a little. I am trying to compile my stylesheets, and have Foundation 4 (the minimalized version) in there. It is taking a LONG time to compile. I have been waiting on it for the last 45 minutes.
I have ditched the SASS compiling feature. It failed to compile and crashed my server.
Moving on, I have put in a script bundle into my webforms site and I got this error:
What do you think?
@Brad looks like it can't find the namespace
Try adding
in your web.config
to the
Cheers, Tim
Hey Tim,
You lost me buddy. I don't think that your answer went through as you expected. I am kind of following you. Can you send me the answer again?
Thanks and Regards
I see what you are talking about now Tim. When I was having problems with the package early on, several suggestions were to comment out a part of the web.config file. So I simply just uncommented the part and I am good to go. Here is the part that I am referring to:
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.