2
Vote

Config files are not auto mashed if source files are in a different directory

description

As reported by various others, the config file is not automatically regenerated.

This is a different bug to the one that was fixed a while back. This one only occurs when the source files are not in the same directory as the config file.

This is a very old bug, so I dearly hope it can be fixed. I tried the trunk code, but the problem is still there.

file attachments

comments

andyedinborough wrote Dec 5, 2011 at 3:31 PM

This should be fixed. This is quite a common scenario for me. I did find another issue related to this, where config files may not be refreshed when a source file changes, but it didn't matter what directory they were in. Please try the latest source (http://chirpy.codeplex.com/SourceControl/changeset/changes/81fbfb2db28d), and if there's still a problem, please let me know.

bugmenot2 wrote Dec 5, 2011 at 4:34 PM

Thanks for working on it. I'm going around in circles, trying to get it to compile, so many references and dependencies... Is there perhaps a build server on here from which I can grab the binaries? If not, can I just drop some of the binaries into my VS addins directory, or do I need to do the formal install from the msi (that's the compile I can't get to work).

andyedinborough wrote Dec 5, 2011 at 4:53 PM

You can just drop the binary (Chirp.dll) into your My Documents/Visual Studio 2010/Addins directory. I've also attached my latest build.

bugmenot2 wrote Dec 5, 2011 at 6:03 PM

I used your binaries, but unfortunately they didn't have the desired effect, in fact, mashing didn't work at all. I'm going to try compiling the main project again to get the required Chirpy.dll.

bugmenot2 wrote Dec 5, 2011 at 6:26 PM

Nope, my build didn't work at all either. I compiled the main project, and copied the TempChirp.dll and pdb to the VS folder, and renamed them "Chirpy.dll" and pdb. Mashing doesn't work at all for some reason. I reverted back to changeset b448c4bb5d24.

andyedinborough wrote Dec 5, 2011 at 6:44 PM

bugmenot2 wrote Dec 5, 2011 at 9:20 PM

Okay, what happens now is that the auto-mashing still doesn't work (when dependency is in a different directory to the config file), so as before I need to manually save the ".config" file, and then it mashes all the stuff within. Another bug that may interest you: with this version, as soon as I install it and reopen my solution, all my mashed ".css" and ".js" files are still there, but it kills my minified files ".min.css" and ".min.js" files. When I manually save the config, it makes no difference, it only mashes the first "FileGroup"--my first is "Minify=False" and the second is "Minify=True", and so it only mashes the first one. Maybe this is related to the dependency problem?

bugmenot2 wrote Dec 10, 2011 at 10:16 PM

Okay finally managed to compile from the trunk and everything is back to "normal" (so ignore my last comment as it's probably something to do with that msi). But, the dependency bug is still there.

bugmenot2 wrote Dec 11, 2011 at 7:42 PM

Spoke to soon, that trashing of the minified files bug is back. I cannot unfortunately replicate the bug yet. However it may be an unrelated bug. It only occurs in the latest version.