Stop sign icon in VS2005 Express solution explorer - visual-studio-2005

What does a small stop sign icon on a file in solution explorer mean? Someone asked the same question a year ago Original Question but the answer provided is of no help.
The icon looks like this:
Suffice to say that the sign is not one presented in the VS documentation and is a UK Stop sign (red circle with a white horizontal bar) not a US one.
The project is WebKit and the build process cannot find AuthenticationCF.h even though the file is present. I presume the sign might shed some light on this.
Thanks,
Andy

Actually, that icon indicates that the file is not set to build for your configuration. Double check by right clicking and clicking properties on the file. You will notice (probably) that the first item, "exclude from build" is set to "yes". Set it to no and the icon will go away. Now, this doesn't address why it wasn't set to build and you might run into some issues getting it to build with the includes and libs you have for a certain project, but that is what the icon means.

From MSDN:
Represents an item that is not under Team Foundation version control because the user has explicitly excluded the item from version control.
Note:
The linked page is essentially the same one from the answer to the "original question", but simply the most up-to-date visual studio one.

Related

Ask and answer dialogs don't appear after being compiled

In Windows 10, everything works perfectly in the Livecode editor (64 bit). However, after building/compiling, ask and answer dialogs are hidden or behind other items in the stack and do not show.
How can I fix this? I need answer and ask dialogs to appear like they should. I tried 32 bit - same problem.
I can't seem to find anything in the build options that would fix this.
Thank you for any help.
Mike
It is possible that the ask and answer dialog assets are not being included in the build. Try this:
Open the Standalone Application Settings from the File menu.
Go to the General tab.
Click the radio button "Select inclusions for the standalone application".
Go to the Inclusions tab.
Scroll down until you find the Answer Dialog and Ask Dialog options, and check those.
Re-build your project and see if that solves the problem. Please note that if you choose to select inclusions manually you will have to check all of the libraries, widgets, and other assets that you are using in the stack.
When the "Search for required inclusions" option is chosen in the General tab, the Standalone Application Builder is supposed to scan the stack contents and include everything that's needed automatically. But it doesn't always catch everything, so many experienced LiveCode developers always do this step manually.

Show solution name in menu bar in full screen Visual Studio

When having Visual studio (2017) in full screen (shift-alt-enter) the solution's name is not visible. Has anyone found a way to append it to the menu?
One can open the solution explorer and scroll to the top but I would like to be able to see the solution's name without manual interaction.
Change the solution name in the solution explorer, then clean the solution and rebuild it and it should show up there.
We are experiencing an outage in the South Central region right now,
which may very well be the cause of your issue.
You can check the Azure Status page for updates.
I am using a plugin to do something similar.
Meet file path on footer. This plugin, will display the full path of your file (that includes your solution) and works of course even while on fullscreen mode. Plus, you got an easy way to visit the folder.

Can I get VS2010 to look at VSS when I click Open Project?

My VS2010 environment has the start page come up if I'm not opening a solution. From there, I can open one of the several items on the recent projects list or I can open a project from the link/button in the upper left. When I do that, I get an Open Project dialog that's pointed at my C:\workingvss (which is a convention that everyone on my team follows for where our code lives locally). But I virtually always want to browse to the project in a VSS database and I have to scroll up in the left-hand pane of the dialog to bring 'Microsoft Visual SourceSafe' into visibility. It seems dumb that I can't make it just start at the top of the pane, but if there's a way, I haven't been able to figure out how.
So I'm turning to you. Is there something I can do to avoid this click and drag every time I want to open a project?
I realize it's defaulting to the Projects location parameter set through Tools > Options > Projects and Solutions > General. But I think I need to leave that as is because I do want my stuff saved to that location during checkout.
I also think that if I removed ten (in my case) folders from the root of my C:, the left pane would show my VSS option, but I don't think that's even possible in this machine's case and not a reasonable solution in any case.
My question is related to, but not a duplicate of, How to change the default open file dialog path.
Thanks for your time!
This isn't a great answer, but it's my current no-tech work-around. If I make the Open Project dialog large enough to accommodate all of the lines it wants to display, then my VSS line is visible and I don't have to navigate to it. Luckily, Visual Studio remembers the size from use to use.

Visual Studio: quick access to most used files

The solution I work on is quite big so it can require a lot of clicks to get to the desired file. I spend 90% of the time working with 8-10 files from this solution so it would be really convenient to have some kind of "Favorites" in my solution so I could jump to the most used files quickly. "Recent files" doesn't cut it, so maybe you know some extensions for VS2010 that do that? Google didn't provide any good options so I decided to give it a shot here and ask what do you use.
Thanks in advance
It's not quite what you asked for, but it'll help endlessly:
In vanilla VS2010, hit Ctrl-Comma (by default) for the "Navigate To" window. You can type a partial file, class or method name and it'll show you a list of where that appears in your solution, and you can open directly from there.
The DevExpress plugins also have a "Recently Used File" window (Ctrl-Shift-Period by default, I think) that does similar, but only shows files you've recently used (not classes or methods). I have to say, though, I've not used that since I've had VS2010.
Wow! A question since 2011 that is still valid to date.
From View Menu click Bookmark Window
open your favorite file
click any line - preferably the beginning of the file
from the Bookmarks Window, click the icon "Toggle a bookmark on the current line."
Very convenient!
Haven't tried this particular feature of the PowerTools myself, but it could do the trick:
http://blogs.msdn.com/b/visualstudio/archive/2010/08/03/quick-access-extension.aspx

Visual Studio 2005 not building solutions

I have a solution with about 20 projects (that use Devexpress controls) in and when I do a normal solution build (ctrl-shift-B) it says everything is completed sucessfully when in actualy fact it has done nothing. To get it to build i have to right click on the solution and use the batch build option.
I've tried deleting the solution and regetting from TFS and i've even gone as far as reinstalling VS!
Anyone got any clues as to what is going wrong?
Sorry should have added that also tried to build from the main menus aswell.
I've had similar issues. It's a long shot, but right-click your solution and go to Properties -> Configuration Properties. Check to make sure all of your projects have the "Build" option checked.
Perhaps Ctrl+Shift+B has been assigned to one of the "check-to-see-if-it-is-needed-before-building" type of functions?
Check in the keyboard setting:
Right-click the toolbar
Select Customize in the popup menu
Click the Keyboard button in the lower right corner of the dialog
In the new dialog, in the "Press shortcut keys", a bit to the right and below the center, hit Ctrl+Shift+B
Verify that it is bound to Build.BuildSolution
at least that is what it is bound to for me. I notice there is an action named Build.RebuildSolution as well, you should experiment.

Resources