New answers tagged windows
8
Windows Installer applications are widely used to install internal business applications in environments using Windows. You should also ask yourself whether over the application's life it will likely ever need to be updated, patched, repaired, or cleanly removed from user's systems. In many cases the answer is "yes" - in which case having a properly ...
18
An installer always makes sense, if deployment requires anything more complicated than copying the relevant file(s) to some folder and running the EXE. If there are additional steps that need to be taken to set the product up properly, there's two ways to go about it.
You can write out a list for someone to follow. Humans being humans, someone's bound to ...
10
Wyatt takes off his programmer hat and puts on his Director of IT hat
If this is an internal line of business application then you only need aim at one environment -- said business. I would call the head of IT and ask him how they would like to manage deployment. IT departments have been dealing with this for a while so they might have a strong preference ...
6
As with all engineering decisions, it depends.
Probably the most important factor is to understand who the consumer of your installation process is and what skillset the development team has.
Since it's internal, I assume it's deployed by an internal IT department. They are probably no strangers to command shells.
Graphical install wizards are useful for ...
0
I couldn't see exactly which part of 'theForger's Win32 tutorial' you were at, so I am guessing a little here:
To 'change the scene' by showing and hiding buttons, you'll need to call something like ShowWindow(hwndButton, SW_HIDE) for each button you with to hide and use SW_SHOW if you wish to show them. If you have kept an array of the 'colour buttons', ...
-1
Here's a super basic intro on navigating through Windows from the command line:
http://www.computerhope.com/issues/chusedos.htm
Here's the MSDN reference, which has excellent documentation on more shell functions than you'll ever need:
http://technet.microsoft.com/en-us/library/bb490890.aspx
In addition, here's the command line documentation for the ...
0
Not working in product development but clearly microsoft windows for good years will still be developed in C and C + +. This is because the languages allow / provide access to hardware to a safe level instruction. C # runs on MSIL and has no goal of being language OS.
3
C++ gives you access to the underlying hardware, something C# can't provide. So for the foreseeable future, Windows will be built in C++ (as parts as still built in assembly where raw performance and interrupt handling are necessary).
As a proof-of-concept, Microsoft Research built Singularity, a C#-based operating system. It uses a superset of C# called ...
0
In direct answer to your question, I bet you'd find that most of Windows pre-dates C# in any case.
Who's to say what will happen in the future? I've seen so many revolutionary ideas from MS over the last 25 years that I've lost count.
But I read somewhere that VS2012 (the gui at least) was entirely rewritten in C# and WPF, so maybe you could take that as ...
-2
At the time, there were no serious competitors to C/C++ in systems programming and now it's a legacy codebase that would probably cost a lot to port. C# also did not exist back then. For the record, there are attempts to turn .NET into an OS platform but these are not Microsoft projects.
0
Note that you can cross compile using GCC, with the right flags and compiler options, and an install of mingw, you can compile Windows binaries on Linux (obviously you won;t be able to run them on Linux unless you install wine)
For a command line app, you should be ok - it depends how many Windows-specific system calls you make that will have to be replaced ...
3
The first thing to remember is that, although C++ source code can be ported between Linux and Windows, the compiled binaries can't be exchanged (at least not without using emulation software).
To create a portable application, your best option is to stay with standard C++ code and portable libraries. For the libraries, you can either build them yourself ...
2
It depends on how you program. If you can't get stuff done without MFC or some other MS library then you will find it difficult. If you tend to use Open source libraries I doubt you would notice the difference.
As far as your second question goes it will limit you some, because some companies are Linux only. I have mostly worked on windows ...
1
To answer your questions:
Not necessarily. Programming with Windows over the last 20 years has required lots of learning of essentially new platforms (Win32, MFC, COM, .NET, WPF, C to C++ to C#, etc.). If you can learn those, you can learn Unix. It's still just programming.
One thing that might be difficult is the different application domains common on ...
3
You can take it in stages if you have the time. The nice thing about Linux development is almost all the tools are free. Start by trying a cross platform IDE like Qt Creator on Windows. Then it's a relatively seamless transition to using Qt Creator on Linux. Then you can learn makefiles and configure and such later as you need them.
On the other hand, ...
2
Let's say you guess Broadband. Now, what speed is the broadband? On a bad day (to use an example, my house for several years) it can be about 2 MiB/s. If you have 3 people trying to use the internet, that can be a problem. So guessing "Broadband at 20 MiB/s" is a dangerous bet, because people will see the massive amount of bandwidth, decide that it will take ...
Top 50 recent answers are included
