This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I've been using Web Workbench for editing SASS files and generating the corresponding css output. It's in quite a large project with 30-35 SASS files, everything was working perfectly until today. All of a sudden it has changed all the output files to <name>1.css instead of <name>.css, so for example main.sass generates main1.css. I've tried: 1. Deleting all css files Each time it after re-generating it produces <name>1.css instead of the expected <name>.css Does anyone know what I can do to resolve this? Thanks in advance. |
|
|
|
|
Doh! I forgot to do the most obvious thing. Opening the .csproj and manually changing the names inside the "LastGenOutput" tags allowed me to force it to generate the correct names again. Not quite sure why it happened in the first place though. |
|
|
|
|
I've never been able to find out what causes this. It is a problem with the Visual Studio infrastructure and can affect all custom tools. It seems that once in a while VS incorrectly decides that the correct file name is already in use, 'fixes' it by sticking a '1' on the end and then remembers its mistake with great tenacity and determination. The solution, as you've found, is to go into the project file and correct or delete the LastGenOutput element. |
|
|
|
|
Yeah I've been getting the same thing too, but only for one out of the 5 scss files in my project. Very frustrating, but glad to find a solution. On an unrelated note, the "register" page is annoying too. I tried signing up to the forum and kept getting a generic "something blew up" message before finally working out NoScript was hiding a CAPTCHA on the registration form. Anyway... free product which 99.9% of the time works great, can't complain too much! |
|
|
|
|
I had just found another workaround. In Properties of "coffee/scss/..." file just remove value from Custom Tool property, manually delete generated files and return Custom Tool value. It should again generate correctly. At least this works for me and it's less paiful than opening csproj file. |
|
|
|
