I have RTM version of VS 2012, and it's great - but intellisense in VS11 in CSS editor doesn't suggest parameter info, but ... something else, I'm not quite sure what is that actually, it looks like some sample.
To be clear, this is what I get (start VS11 without solution, FILE -> New -> File, file type Styles Sheet):
And this is what I get in VS10 (and what I'd really like to have in VS11):
This is just a sample with "margin"; I tried resetting preferences, clean install of VS11, etc. It behaves the same way with or without solution.
I suspect the problem is between keyboard and chair, but I didn't find any clue in VS11 preferences, or googling any combination of "intellisense css visual studio 2012", etc.
Thanks,
Robert
That is the correct suggestion!.. It is basically giving you an example of what you can put as a value.
It is very useful for other CSS3 properties where the value is more complex.
Related
When i'm typing code, the intellisense comes up to predict code, but before i can choose something in the list, its already gone. I know that you can use crtl+spacebar to bring it back up. But it's pretty annoying.
Does someone knows how to fix this?
(I'm using visual studio 17.3.1 (.Net - C#))
It is likely that this problem is caused by vs extension. You can try to disable the extensions and try again. If it doesn't work you can choose to reinstall Visual Studio.
I'm missing two checkboxes for defining constants in my properties screen. Am I missing something?
It should look like this
I'm using a Microsoft.NET.Sdk.Web project in net6.0
Somewhere along the way, Visual Studio streamlined these options to what you are seeing instead of what you are expecting to see. Actually, I don't think this is a Visual Studio-specific change, but rather it depends on what kind of project and what SDK you are using - those being:
.NET Framework
.NET (.NET Core)
I am guessing you are coming from one of my other answers, which sparked you to ask this question. In my post, that screenshot is from a .NET Framework project. I should have probably been slightly more specific in my reply to you. In your project, you are clearly using .NET 6 (as you mentioned above). Because of that, your properties menu looks way different. This is the streamlining I am talking about.
So where are your checkboxes for defining DEBUG and TRACE constants? They are gone! However, you are looking right at the control that replaced them - or rather, you are looking at how these controls work now. Essentially, the $(DefineConstants) replaces these checkboxes, and you can specify additional constants in the same textbox, separating each by a semicolon. If you hover over the "Conditional compilation symbols" controls and click the gear icon, you can toggle it to vary by configuration, which I think is more clear and useful to do:
Then, if you wish to add custom constants, simply add them to the configurations. In the below screenshot, I added an ONLY_DEBUG to the Debug configuration, and an ONLY_Release in the Release configuration:
In the code, you can use them as so:
Microsoft Documentation can be found here.
I am currently learning about Xamarin.Forms and XAML using Visual Studio 2017. Intellisense seems to be working for XAML files for the most part, but there is at least one tag it doesn't autocomplete, which is OnPlatform. And when I manually write the tag, it doesn't autocomplete attributes like x:TypeArguments. However, it compiles and runs just fine with the OnPlatform element.
Is it normal that Intellisense does not work for a (seemingly random) tag? Are there certain tags that are not auto-completed on purpose?
Is it normal that Intellisense does not work for a (seemingly random) tag?
YES. Sadly, Intellisense support for XAML is patchy. It has been for as long as it has existed. As far as I can tell it does indeed seem random whether it works or not, like you say. I'm sorry that this probably isn't the answer you were hoping for.
There are some suggestions around getting xaml, Xamarin and Intellisense working together here but your mileage may vary:
https://forums.xamarin.com/discussion/93148/getting-xaml-intellisense-to-work-vs-2017
Just wondering if anyone knows the answer to this one. I am running VS2015, and some colleagues are running VS2013. We are all running our code through TFS for source-control, and we encounter this issue quite a bit.
When we open a form or a control, not even modifying it, then close it, it will completely restructure the *.Designer.vb file, but not modify any data (at worst, it's simply put the upper casing of True/False to true/false).
This proves an issue as we are becoming increasingly wary of working on the same forms as one another.
Does anyone know a potential fix to this, or if this is a bug of sorts?
Thanks!
The VB code use PascalCased keywords.Even though you write the keywords in lower case and VS would auto-casing to PascalCase.
However,there is a way to change to Lowercase Keywords：
Download Glamour from the GitHub repo.
Install it by drag/dropping the truetype font (.ttf) files in your
%SystemDrive%\Windows\Fonts folder.
Change your text editor font in the Tools > Options > Fonts & Colors
dialog to Glamour.
Select "Keyword" in the "Display Items" list and check the "Bold"
checkbox.
Finally you got this as below:
This method is referenced from Anthony D. Green's Blog. More detail: http://blogs.msdn.com/b/vbteam/archive/2015/04/02/lowercase-keywords-revisited.aspx?PageIndex=1#comments I was wondering anyone of your team are using the lowercase keywords cause this.
I am using Visual Studio 2010 Prof.
In C# I can create my own Enumerator and use it like this:
MyEnum value =
Now, Intellisense will suggest a value of MyEnum.
In VB, when I write:
Dim value As MyEnum =
I get a huge list of every types. When starting to write my enumerator value (could be a word like "sunny") it filters out some types but I would like to have it like in C#. Anyway I will use the MyEnum type and no "String nor Objecte nor IntPtr...".
Any idea?
Screenshot
Also I made a short video:
Video with sample (new)
Regards
Simple, all you have to do is click the "Common" tab at the bottom of the Intellisense drop-down.
To prove it, here's a screenshot of what I see in VS 2010, immediately after typing =:
But, even if you have the "All" tab selected, the values defined in the enum will still be automatically displayed first, and even appear grouped together. You will indeed see all possible members and types, even those that are completely unrelated, but it's still pretty easy to find the ones you want.
And no, I'm not using any third-party add-ins or extensions to achieve the demonstrated feat. As best I can tell, I also haven't reconfigured any relevant options from the default settings.
This is a documented issue in VS 2010, pre-SP1. See: https://connect.microsoft.com/VisualStudio/feedback/details/551699/intellisense-enum-values. It has been fixed in SP1. If you can't install SP1, the only workaround is to use the mouse or Alt + , to switch from the "All" to the "Common" tab.