I just googled on how to use Application Settings and came up with the following
msdn article. It describes to ways to add Application Settings at design time in VS 2010. One using the Project-Properties and a second using the Properies-Window for a selected control.
I tried the second one, but there simply is no node Data or a property ApplicationSettings under it. Is the article outdated? (although it states there that it applies to VS2010) Or have I overlooked something else? I vaguely remember seeing some such property in an older VS version but I am not sure about that.
Edit: My project is a WPF project.
Application setting binding in the Properties window is only supported for Winforms projects, not WPF.
Related
Maybe I'm missing something really obvious, but I can't for the life of me find the information I'm looking for anywhere.
In Visual Studio 2022, when you go to the Project Properties for a .NET Core or .NET Standard project, the new UI uses property evaluation to grab certain properties with a dollar sign syntax (e.g. $(MSBuildProjectName) or $(AssemblyName)) which correspond to MSBuild properties. Immediately below these, it displays the evaluated property:
I'm trying to find out 2 things:
First, where are these properties being sourced from?
Second, is there a documented list of tags that can be used?
The only thing I was able to find that was close was this blog post by McKenna Barlow: https://devblogs.microsoft.com/visualstudio/revamped-project-properties-ui/
Any help to find this documentation is appreciated, since I have spent considerable time searching on the learn.microsoft.com site without success.
Just upgraded to Visual Studio 2015 and the Code Definition Window is not working.It just says "No definition selected" no matter what I select. Project is Windows Forms written in C#.
Go to Definition and Peek Definition are working fine
Went back to VS2013 to try it out and it's still working there
Tried to make a brand new project in VS2015 to see if it was project related, but it was not
Checked with a couple of colleagues and it wasn't working for them either
I have a feeling this is either a bug in VS2015 or some sort of configuration change.
Anyone found a way to configure it, or any sort of work around to get it up and running again?
I got a reply from Microsoft on my Bug report. Turns out it's not implemented and possibly never will be:
Hi,
Based on the fact that Peek Definition was introduced in VS2013,
combined with telemetry data that shows that only a tiny percentage of
users ever display the Code Definition Window, we decided not to
implement support for it as part of Roslyn. I've filed an issue on our
GitHub project to consider resurrecting it.
Thanks for the report!
-- Kevin Pilch-Bisson Visual Studio Managed Languages
Here´s the github issue Kevin created in response to my bug report in July: https://github.com/dotnet/roslyn/issues/4224
Looks like they just merged a fix for this into Roslyn:
https://github.com/dotnet/roslyn/pull/56102
I am having trouble tracking down information regarding extending Intellisense. It looks like creating a plugin for VS 2010 or Resharper would do the trick. However, I can't find any documentation for adding items to the intellisense dropdown.
This post got pretty close: How to extend IntelliSense items?
But I couldn't find any documentation for the interfaces or classes being used.
What I am trying to do is to read from an XML file, and add those tags as part of the results that show up in intellisense in the C# code (not in XML).
The part of the R# Plugin Development Guide concerning Code Completion (i.e., IntelliSense) is on our todo list but has not yet been written. When done, it should be available here. While we're working on that, feel free to email me dn at jetbrains dot com, and I'll try to help you out with any queries you might have.
I was wondering if there's anything like Eclipse Perspectives in Visual Studio (2008 or 2010).
For those unfamiliar with Eclipse, here's a definition of Perspectives:
A perspective is a visual container
for a set of views and editors
(parts). These parts exist wholly
within the perspective and are not
shared. A perspective is also like a
page within a book. It exists within
a window along with any number of
other perspectives and, like a page
within a book, only one perspective is
visible at any time.
Let me give you a visual example:
Java Perspective:
SVN Repository Perspective:
Maybe there is nothing like that straight out of the box, but with some plugin. If that's the case, it'll also be a valid answer.
Thanks for your time.
I used Brian's blog post as a starting point and made a VS2010 extension: http://perspectives.codeplex.com/
More info here: http://csharpening.net/blog/?p=292
It's probably not as complete as the VSWindowManager but lets you save your configurations and create new ones. Let me know if it works out!
I found this http://vswindowmanager.codeplex.com/ but it's for 2005.. there is a branch for 2008 in the source code but i don't know if it works... I think I'll give it a try and post any results...
It would be great if it works also for 2010!!! When you work in 1024*768 it's really annoying to rezise the windows every two seconds!!!
Good luck!!
You can check out my blog post which provides the ability to list and switch window layouts in Vs2008 and Vs2010: http://www.brianschmitt.com/2010/09/save-and-change-tool-layout-in-visual.html
Is there someway to get VS 2008 intellisense to default to Properties over Classes in a name collision?
Example:
Within my scope I have a property Foo, but I'm also using a class Foo. When writing code, if I start to type F o, VS2008 intellisense will think I mean the class Foo. I want it to think I mean the property Foo instead.
Unfortunately no this is not possible. Customization of the priority of value categories like classes / properties is not supported
There is no possibility in VS2010 and not even in ReSharper 5.0 to deal with this issue. It won't be a feature of ReSharper 6.0 as well, according to JetBrains. I use a different name for the property, when it starts making me aggressive and refactor it after I've done most of the work.
Update:
I reported the issue to JetBrains some time ago and I just got an eMail that the feature has been added and will be available in Release 6.1. So good news for ReSharper users on this one!
http://youtrack.jetbrains.net/issue/RSRP-273067?projectKey=RSRP
I was thinking the exact same thing today.
While the functionality is not in vanilla VS, it is quite possible to modify some code to add this functionality. For example, the XAML Presenter, probably named after the presenter component that you have to modify does something similiar.XAML Presenter
It narrows by namespace and sorts by attribute type. Basically, I'm just gonna take the list the Intellisense Completion Source gives and sort the list. Sounds simple enough.
More challenging is implementing the UI controls. I hate designing UI controls . . .
Edit:
However, I don't forsee a way to do this without breaking Resharper's Intelllisense features.
Use VS 2010, I suppose? I can't see which situation would make VS put classes over properties, though.