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'm using Visual Studio 2013 and Mindscape Web Workbench version 3.2.1144.23109. I have a website project which I've branched to a different folder in TFS. However, the setting file lists all the included files for javascript minification and combining with absolute paths pointing to the trunk rather than the branches folder. Is there a way to refer to files using relative paths in the settings? I've updated the references in the settings but I still can't force the files to update the combined / minified versions. Is there a way to start it off or is Mindscape not watching the correct files? Regards, John |
|
|
I've removed the WebWorkbench.mswwsettings from the website and re-added the javascript includes I had. The settings view was much faster than before and I was able to add the group although no new WebWorkbench.mswwsettings was created so I suppose this information is now kept somewhere else? The compile for Sass worked but not the javascript file one (minify and combine). However opening the project in Visual studio 2012 then caused the javascript files to be updated. Regards, John |
|
|
Is it possible to strip the project back to just a single JavaScript file which is not being updated correctly? If you are able to send this through I can have a look into what the issue is which is impacting this in 2013.
|
|
|
After having left it for a couple of weeks and returned back to it, it seems it's now working. I think it may have something to do with the number of files (20,000+) that were in the website: the WebWorkbench.mswwsettings is now in a folder higher in the tree (App_Data) which has helped the settings be much faster. It could be that since it was so slow beforehand it could not trigger the compile process in the time I was looking at it. Having tried it on new empty projects and websites, it works fine. The only issues remaining are that:
Regards, John |
|