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
|
since the last web workbench update, i've been getting this error: Web Workbench created output files in the following directories which are not part of the project: * C:\Development\Web Applications\staffnet\trunk\SitefinityThemes\staffnet-boilerplate\App_Themes\Boilerplate\Global Please include these folders to the project using Show Hidden Files and Include In Project. what to i need to do here? |
|
|
The message is just a heads up that when we generated files some of them were generated into a folder that is not currently included in your project. If you dont need to include that folder then you can just ignore the message, otherwise you will want to toggle the "Show all files" button in the solution explorer so you can see all folders and then right click on that folder and include it in the project.
|
|
|
ok, that makes sense. here's my specific situation: win8 vs2012 i'm using sitefinity thunder to edit sitefinity themes. my solution contains the website and the project for the sitefinity themes. the "sitefinity themes" project files are within my website's directory. website/ website/SitefinityThemes/ do i still need to add this folder to my website project even though the "sitefinity themes" project is already part of the same solution? actually, when i right click, i'm not sure what to do. anyhoo, here's a screenshot that might give you more insight. |
|
|
If you expand down that section of the folder structure I expect you will find that the specific sub-folder specified in your earlier post is not actually included in the project, so that is the one you will need to include in order to squelch the warning. As mentioned though, you dont specifically need to include the folder so long as you are happy to ignore the warning - its just there to alert you to the fact that the generated files are not part of the Visual Studio project. This would lead to missing files if you are doing a deploy from within Visual Studio rather than via some external process or agent where it knows to specifically include those files.
|
|
|
this continues our list of frustrations, i can understand now that you explained that there are folders not in the project, although looking in solution explorer with all files showing, we can not find any folders not in the project that mindscape/ww needs to know about. what is more frustrating though is every time ww compiles the sass it checks out the csproj file from vss and there is no reason why it should since we only compiling sass files that already have been added to the project. there is no reason why that file needs to be continually checked out by each developer every time they save a sass change. we spend more time yelling at one another to give us the file back then we do coding. if anyone of the developers gives the file back just so we can compile, it checks out the csproj file again then i for example gets yelled at. . i hope you have a good answer or a fix for it some time so we can all begin using ww again. rick f. rickfessler@gmail.com |
|
|
ok, here we are futher in the directory structure to the one WW says is not in the project. |
|
|
Hi Rick, Im not sure why the .csproj file would be checked out if nothing is being added to the project but unfortunately we leverage the Visual Studio API for source control to handle this type of work so we dont have any control over what it decides to check out. I cant recreate this myself but I am not using VSS so I wonder if this might be a quirk of the VSS provider. Presumably you are not seeing the behavior when editing a file normally when Visual Studio will automatically check out the file for you (it will just check out the file involved)?
|
|
|
Hi Will, Thats interesting, the folder indeed looks to be part of the project but presumably you are still seeing the warning? From the screenshot I am not seeing any files that are not included under that folder either - is that right?
|
|
|
yes, as far as i can tell! so, i've stopped getting the error. that's good news! i'm not sure why, but everything seems to be working fine now. if i did something to fix it, i don't know what it was. :) |
|
|
jeremy, maybe you could start using vss for your development since issues could arise for any developer using vss ? (or subversion or .....). and yes,
but i also know, because we do it, that you can still write modules/methods/etc to 'work around' or 'work with' others API's this is a huge frustration that i hope others either don't mind having in a team setting. don't forget, for anyone thinking about buying a license or two and that are using vss or possibly another source control may have second thoughts if their department has two or more developers. thank you, rick f |
|
|
Hi Rick, We actually use a combination of SVN and Git here but we have not seen this problem. I am not aware of it being a problem on other source control providers for Visual Studio so I suspect this is specific to the VSS provider. If you are seeing this behaviour on any other providers please let us know! :) In terms of working around the Visual Studio API's and doing something more specific to target VSS, this is not something we will be doing as we do need to call the Visual Studio API's as we are currently doing to ensure Visual Studio correctly registers the changes. Additionally because VSS is not supported we would not want to take a dependancy on it.
|
|
|
I get this warning now, constantly (every time I save one of my .scss files). It is very annoying. I have a config.rb file with the following settings for Compass:
Regardless of these settings, I see the following output appear in the Output window after it pops up over my VS work.
I'd like to note that there is no such \Website\content\content\styles folder created. The generated files are going into \Website\content\styles (without the double 'content' path); just as they should be. Yet, I continue to get this warning. Everything works fine, but the warning is incessantly annoying. |
|
|
Thanks for reporting this, this is a bug in the reporting of the missing folder and I have added a fix for this. This will be available in the next nightly build.
|
|