Is it possible to configure Xcode to have a similar appearance to Visual Studio or another IDE? I mean, when working with .Net Core, the IDE is very intuitive, for example when it comes to determining the type of a var or let. Also, in Visual Studio you can easily see the references of a var, let or function throughout your code, making the experience of using it better than in Xcode. So I would like to know if it is possible to make Xcode have a similar appearance to Visual Studio.
Related
I am used to working with intelij and even after working with visual studio I still have problems using it effectively. It is generally annoying for developer to learn new shortcuts wen switching IDE. So. Is there an easy way to make Visual Studio feel like Intelij or any other IDE? and if there is no way. Could that be done in theory?
(I am not referring to how Visual studio looks like. Just the Shortcuts and general control of the IDE)
Hot Keys extension lets you load IntelliJ IDEA keyboard shortcuts to Visual Studio.
We are using a commercial software that has its own scripting language with which you can customize the product. It is very tedious to write code in it without any help from an IDE and it has its own compiler.
Is it possible to use Visual Studio and create an environment for me to write scripts in this language and get the help of intellisense and syntax highlightning and other good things you find in an IDE? Ideally I would like to bind a button in VS to launch the external compiler and compile the code so I don't have to switch windows all the time as well.
If this is possible is it a very hard thing to accomplish?
Yes, this is certainly possible. You need to create a Visual Studio Shell add-in with custom language services and text editors. You need to install the appropriate Visual Studio SDK and then you'd continue to:
Create a custom Editor and/or designer
Add a language service
Add Project and Item templates
You're allowed to ship Visual Studio Isolated Shell with your application (license required and there are some limitations) so that your users don't need to have Visual Studio Professional installed.
There are a number of open-source projects that provide a custom editor, language services etc in Visual Studio, these could provide a nice place to research how things are done, next to teh Visual Studio SDK documentation:
PyTools, which is a Visual Studio editor for IronPython
Phalanger, which contains a Visual Studio editor for PHP
PoShTools, a Visual Studio service for PowerShell editing right inside Visual Studio
You'll probably want to dig into MsBuild as well, since Visual Studio will expect you to create a project file if you want to edit a collection of files and compile them. MsBuild could in turn call your own compiler, like it calls csc to compile C# code for example.
Creating Project Types
My question is rather simple. I have a project using a few external libraries documented with doxygen.
Is it possible, with Visual Studio (or with the help of an extension) to view to doc associated with a class or a method by clicking on it or via a keyboard shortcut, all without leaving Visual Studio?
I've stumbled across Doxygen Browser Add-in for Visual Studio, which looks quite good. Compatible with most currently used Visual Studio versions.
Other than that, there's a more DIY solution avaialble by (apparently quickly) writing up a Visual Studio extension, as described here.
I want to use Visual Studio (maybe Isolated Shell) to create a custom IDE for programming a custom ARM-based device in C. The device has no OS and is being used like a microcontroller.
Atmel's AVR Studio 5 uses the Visual Studio 2010 Isolated Shell and I would like to do something similar. I am currently using a gcc-based ARM compiler.
I've already been through MSDN's documentation for extending Visual Studio, but I can't find anything specific to this task. Can someone give me an idea of how to approach this? For example, is there some way for me to leverage the Visual C++ editor without having to use Babel to re-teach Visual Studio about C?
MSDN documentation is not enough if you want to create a new IDE in fact. My personal suggestion is that you learn from existing large samples, such as this Python IDE,
http://pytools.codeplex.com/
It is designed by Microsoft, so it provides much useful information that does not appear in MSDN.
However, reusing Visual C++ editor means you cannot use only Visual Studio 2010 Isolated Shell (I think), as that may require some assemblies that only full Visual Studio has.
This is easily one of the most annoying "features" of Visual Studio in its history and I don't understand why it exists -- ever.
Why would a CodePlex project need to care what version of Visual Studio I am using?
Off the top of my head, the only thing I can think of is that some versions of Visual Studio might introspect assemblies searching for attributes to determine what to display in "Visual Designers" and "Property Editors". But why would that cause Visual Studio to not be able to open the project and allow me to browse its contents and compile?
It seems to me like Open Source in .NET is somewhat limited by the stupid dependency management exhibited by Visual Studio. In other words, if I am using Visual Studio 2008 and you are using Visual Studio 2010, then we have different solution files.
http://blogs.msdn.com/b/visualstudio/archive/2010/03/15/why-does-visual-studio-2010-convert-my-projects.aspx
Here's an example from the site as to why Visual Studio converts your projects to 2010 format.
For instance, Visual Studio runs
custom tools such as single file
generators for designers in order to
output code representing the changes
made to the designer. Many of these
custom tools are upgraded or
completely replaced in the newer IDE.
During conversion, the IDE knows which
custom tools to replace or upgrade. In
order to make round-tripping work, VS
would need old and new custom tools to
understand each other so as to ensure
that old and new designers can work
side by side. Other than designers,
the following files would also be
affected: resource editors, wizards,
code snippets, item and project
templates, diagramming and modeling
tools, and many more.tools, and many more.
Since 2010 knows about what tools 2008 has, it can convert forward to be compatible with the custom tools 2010 uses. 2008 has no idea about what 2010 is using, how could it? Therefore, it is impossible to convert backwards since it doesn't know what it needs to convert, nor how to.
I believe the purpose of this touches on what you stated in your comments. If you are using 2008 and I 2010 and I compile it, how could you possibly run it again? 2010 is backwards compatible but 2008 has no way to make itself forward compatible.
Thus, by recompiling the project in 2010 I ensure that no 2008 user may mistakenly think they can compile it.