An awesome feature has arrived: VS IDE support!!
Moderator: Moderator Team
Re: An awesome feature has arrived: VS IDE support!!
NT component added (last changes) that means to reactos?, greetings.
-
- Posts: 128
- Joined: Sat Dec 22, 2012 7:36 am
Re: An awesome feature has arrived: VS IDE support!!
Allowing ReactOS to be built using Visual Studio is a most excellent accomplishment. There are programmers throughout the world, both professionals and hobbyists, who use Visual Studio as their primary integrated development environment (IDE). These programmers will find comfort in using a familiar tool for ReactOS development.
Given that Visual Studio Express is free, one must conclude that this new feature from the ReactOS organization will accelerate adoption of ReactOS as a platform-of-choice for open, innovative, and liberating software applications on Intel/AMD x86 machines and beyond.
Congratulations!
And thanks to Amine for all his hard work to make this possible!
Given that Visual Studio Express is free, one must conclude that this new feature from the ReactOS organization will accelerate adoption of ReactOS as a platform-of-choice for open, innovative, and liberating software applications on Intel/AMD x86 machines and beyond.
Congratulations!
And thanks to Amine for all his hard work to make this possible!
Re: An awesome feature has arrived: VS IDE support!!
What a nice surprise!
thank you Amine!!!
thank you Amine!!!
Re: An awesome feature has arrived: VS IDE support!!
I'd call it maybe "the mother of future features". To quote Faraday, "the use of this is as much as from a newborn child". - Well, good luck with it, I am looking forward to what this will lead to.
Re: An awesome feature has arrived: VS IDE support!!
This is a part of a long-term action on reviewing component list. Kernel as component is no more, replaced by NTCore - which is more than just the kernel, it also includes other low level parts (HAL, ntdll etc). Patches has been replacted by PATCH label and Win32 - by Win32SS component.manuel wrote:NT component added (last changes) that means to reactos?, greetings.
Re: An awesome feature has arrived: VS IDE support!!
Ahh, tanks for your reply
Re: An awesome feature has arrived: VS IDE support!!
This should spead up development.
Stay frosty, Tony Bark.
Re: An awesome feature has arrived: VS IDE support!!
Can somebody please explain why this is so important?
Re: An awesome feature has arrived: VS IDE support!!
usually you have to open the Build Environment and build ReactOS via Commandline.Pesho wrote:Can somebody please explain why this is so important?
Now you can Build it inside a comfortable Development environment.
Also you have automatic Error recognisation, you can directly connect to an SVN Server and much much more.
I think the best is that you google about visual Studio and it's benefits then you can see which wonderfull things the devs can use now.
Re: An awesome feature has arrived: VS IDE support!!
Easier debugging.Pesho wrote:Can somebody please explain why this is so important?
And even special VS tool that analyzes static and dynamic code
-
- Posts: 128
- Joined: Sat Dec 22, 2012 7:36 am
Re: An awesome feature has arrived: VS IDE support!!
In Linux Land a programmer might use apt-get, gcc, gas, ld, make, mv, emacs, cp, ssh, etc. all in one session. By contrast, a typical Visual Studio programmer might never leave the IDE in six months. This is true even for programmers who got their start in Unix. The IDE is like a comfortable cruise ship. Once you experience it, and learn how to control it, you really do not want to go back to make files. There is really no comparison between the leverage gained by an industrial-strength IDE, and make files. There are a lot of other little things, like multi-core parallel builds, fast edit-compile-link-debug cycles, etc.Can somebody please explain why this is so important?
There are very large number of programmers, both novices and advanced, who use Visual Studio as their primary development environment. This was true even before Visual Studio Express, but with VS Express, it is even more true. Many of these people would likely participate in ReactOS development, but have not (or disengaged) because the ratio of actual work / build frustration was too low.
And finally, I need to say one thing, because the counter-argument to this point of view is typically, "If they cannot set up their own make files and type a few simple commands...yada..."
It's not that they cannot. It is that they do not want do. There is a difference. If you have trouble appreciating this, imagine having to run Visual Studio, from the Linux command-line, then waiting for a pop-up dialog box, then clicking on a radio-button then a CANCEL button, to get it to go away. It would take 3 seconds to accomplish. Certainly not difficult. And you would hate it, because (1) it is intuitively unnecessary and (2) it is quite foreign to what you are accustomed to.
In situations where it is feasible to eliminate an inconvenience that affects a large number, especially one that might discourage new developers from even getting started, we should take it.
-
- Posts: 420
- Joined: Tue Sep 16, 2008 1:13 pm
Re: An awesome feature has arrived: VS IDE support!!
On a scale from 1 to 10 (10 is best):
To some who may judge it:
Which rating would this good news be ? - first "feeling" without long thinking !
To some who may judge it:
Which rating would this good news be ? - first "feeling" without long thinking !
Re: An awesome feature has arrived: VS IDE support!!
9.5 for the Development pov. Maybe the user won't notice it, as it is a not a ReactOS feature, but does Devs life easier and faster.wildschwein wrote:On a scale from 1 to 10 (10 is best):
To some who may judge it:
Which rating would this good news be ? - first "feeling" without long thinking !
Re: An awesome feature has arrived: VS IDE support!!
a nice thing that could be used now is (visual studio/virtual machine debug integration):
http://blogs.vmware.com/workstation/200 ... vmwar.html
i also came accross (VisualDDK is a Visual Studio extension that allows developing and debugging Windows kernel-mode drivers.)
http://visualddk.sysprogs.org/
also:
http://virtualkd.sysprogs.org/
best thing it's open source
could this be usefull to reactos and is there already such a system for reactos ?
http://blogs.vmware.com/workstation/200 ... vmwar.html
i also came accross (VisualDDK is a Visual Studio extension that allows developing and debugging Windows kernel-mode drivers.)
http://visualddk.sysprogs.org/
also:
http://virtualkd.sysprogs.org/
best thing it's open source
could this be usefull to reactos and is there already such a system for reactos ?
-
- Posts: 128
- Joined: Sat Dec 22, 2012 7:36 am
Re: An awesome feature has arrived: VS IDE support!!
It is no secret that I have been a cheer-leader of Visual Studio integration for ReactOS over the past month. After a survey of Visual Studio tools, I concluded, with the help of others, that the "sweet spot" for using Visual Studio against ReactOS is Visual Studio 2012....could this be usefull to reactos and is there already such a system for reactos
Here is why:
- Visual Studio 2012 allows a developer to debug kernel-mode device drivers, inside a VM or otherwise, just as s/he would a user-mode application. The presentation to the developer is nearly identical, with the setting of breakpoints, Intellisense, etc. all active and available. Imagine how convenient it would be to set breakpoints in both a kernel-mode driver and a user-mode app. You can watch IRP's travel up the I/O stack, block on a kernel-mode service routine, keep going, and block again, this time, in user-mode, when the IRP is completed, at say, ReadFile.
- With previous versions of Visual Studio, the build process for device drivers was not the same as the build process for user-mode applications. A command-line-oriented process was used for device drivers, and the IDE was used for user-mode applications. This has changed. Under the new model, the IDE is used to build all types of executables (.EXE, .DLL, .SYS, etc.), including device drivers. IDE-only builds have been possible essentially since the mid-1990's, but now Microsoft actually sanctions it.
- Switching among compiling for x86_32, x86_64, and ARM is as simple as selecting the appropriate CPU type from a drop-down list.
- Visual Studio 2012 will load the .vcxproj files that were created by Visual Studio 2010 without altering them, allowing them to be reloaded by VS2010 after they have been edited by VS2012.
I am still working on my own set-up to get all of these things working together under VS2012.
Who is online
Users browsing this forum: Ahrefs [Bot] and 27 guests