My company uses a flavour of GIT for moving source code from your local system to the repository at the desired location (which later deploys and stuff , its a server basically) and the support for that tool is BAD. It uses the commandline and its very tedious to use it . I want to build somthing similar to tortoiseSVN / tortoiseGIT for this purpose and i am looking for a starting point.
How would i get the overlay icons in the folder ?
How would i be able to do windows explorer integration in the "right" way ?
I'm going to use .Net C# to build this tool.
Thanks in advance for the help!
Cheers.
You can write a Shell Extension! There is a lot to learn, though. Part IX of the complete idiot's guide to shell extensions series explains how to deal with icons.
In general writing IE and Shell extensions in C# isn't supported. Of course, newer versions of the runtime do allow you more flexibility in the area of SxS support. But you're on your own in terms of writing the COM interop and you need to think very carefully about how this will effect other apps that do things like use the file-open dialog.
Related
I want to create a winforms application with text to speech implemented. However, the voices that are available are based on what you have installed on your OS. Is there a way to make sure the end-user also gets the correct voices that are needed, without telling them to install them manually?
This is ofcourse, if you are using SpeechSynthesizer.
If this isn't possible, I would like to know if there is an alternative to a free/open source TTS API that doesn't require your application to be on an Azure platform or being registrated somewhere (Google, TranslatingService and what not).
This is one of those question, where the answer seems so simple and obvious, we are not even certain we understood the question right:
You make a installer.
Part of the installer is to also install those TTS packagages containing the voices.
Done. Everyone using your programm via the installer you provided has the same voices. And that (plus maybe some links in the Programm Registery) is all that Installers do.
Points of note:
of course you need the legal allowance to redistiribute those packages. With some it is clear cut (like the DirectX redistirbuteable). But you need to check the licensing agreement.
older versions of Visual Studio did have a "Installer Project". But as Installer Systems like InstallShield and Windows Installer proliferated, those were cut without replacement.
I am developing an app specifically for Surface Studio - how is it possible to check that the machine is indeed a Surface Studio?
Ideally from within .NET, although perhaps this is information gleaned from the registry, I am not sure.
You can get more info about it by using Win32 Classes, it will help you a lot querying almost everything about your system.
To be easier, you can also download an application provided by Microsoft which allows you to better search the info you are looking for. The information you are looking for is probably located at Win32_ComputerSystem.
Me and two others are starting to make games, we all have some knoledge of C# and VB.Net, we are using C# with the XNA Managed Runtime Environment to make a game.. We have one problem we can't find an answer too though. How do all three of us work on the same project? I saw something about Team Foundation Server, but would that allow us all to work on the project? Or is that just for statistics and time activated builds..
Thanks, Matthew
You need source control. That could be Team Foundation server, it integrates nicely with Visual Studio. Git is also a very popular alternative, but it's more complex.
I started out with SVN server and that was simple and easy for me. You should google for what suits your needs.
Source control is something that runs separately from your project, it has little or nothing to do with your preference of language.
Any source control solution will work to help you manage the project in a team. This includes Team Foundation Server, but also github.com, Bitbucket and other options.
Team Foundation Server is primarily used as a source control tool (can also be used for build management, storing test cases etc.). If you want to maintain a history of the changes to any code, then go ahead with Team Foundation Server or some other source control. A source control would also help you in making local changes and then merging your change with the changes made by others afterwards.
Yes TFS (Team Foundation Server) will help you.
It has a source control, which keeps track of changes made by individual developer and let you merge your changes with code on server or rollback any changes
It provides project management capability, to create user stories and tasks then assign each commit with task to let everyone know that "this change is performed for following task"
and many more ..
I would like you to give me some good resources regarding Windows development of applications that integrates with OS like Application managers, Docks, Task-bar\System tray etc.
Resources like how to interact with particular subsystems are welcome.
Thank you
What you are looking for is information on writing shell extensions. Generally it is not recommended that you write shell extensions in .NET though the landscape might be much better now with Framework 4.0 supporting side by side loading of the framework.
Searching with Bing/Google for shell extension c# will yield a number of results that might be relevant.
As for the docking part of your question, the most reliable way would be to register your application as an Application Desktop Toolbar (AppBar), here is a Code Project article on doing this with C#, it should be a fair starting point. http://www.codeproject.com/KB/dotnet/AppBar.aspx
It appears much of what you would like to know about involves using the Windows API. Its documentation might give you a start: http://msdn.microsoft.com/en-us/library/aa383749(v=vs.85).aspx
I am mainly a java programmer, using linux/os x for as long as i remember. I am extremely comfortable in emacs and usually prefer doing things through command line.
I need to create a internet explorer addon for our next project. I need to intercept url ie is about to download and if they meet certain criteria pass it to our application.
So my questions are,
How can i build a c# project through command line so i can integrate it with our current build process.
Current i have windows 2k installed in a virtual machine that i use for testing. Is there going to be any compatibility problems.
I am assuming i am going to be creating a dll and inject it to ie to intercept url's. Am i on the right track?
Here are responses to your questions:
Use the C# Command Line Compiler. MSDN has an entire section devoted to its use.
Not for an IE add-on. If you plan to do more, using some newer libraries, you may run into problems unless you're running Windows XP or later. For IE addons, 2000 should be fine.
That's the basic idea. I'd refer to the MSDN articles on creating add-ons for IE, such as this one showing how to make custom menus.
Be aware, though, that you'll have a more difficult time if you avoid using Visual Studio (or some other IDE). There is no reason not to use VS, especially since you can use the Express Edition for free. If you're doing that, you can use msbuild instead of csc directly, and it will simplify your build process (even if you build from the command line).
However, the productivity gains from a good IDE will come in handy, especially for C#.
Responses to your questions:
If you use Ant maybe this will help. If you use Maven, maybe this will help. Otherwise, I'd just use MSBuild or NAnt.
Can't say for sure. I would guess that the IE API would be the same on each of the platforms. YMMV.
I'm busy writing an IE addon at work and I'm using SpicIE. It's very straightforward and simplifies the IE API drastically.
I've read in the comments elsewhere that you're not a fan of VS. I would probably use it (or MonoDevelop/SharpDevelop if they can create .csproj) to create the .csproj that can be used as an input to MSBuild. It might save you time rather than having to learn the syntax of the file.
If you give up the IDE, you give up one of the best debuggers on the planet and the best code-completion I've ever seen. Other than the fact that it will be a new system to you, there is no reason to claim that you can develop faster in EMACS. Everything you need is in the IDE, and there are keyboard shortcuts to mostly everything.
If you computer can handle the work load, I really see no good reason not to use Visual Studio.
edit: the newest version of visual studio won't run on anything less than XP sp2, to my recollection. This is most likely because the new versions of .NET won't run on anything lower than that... which would be a huge compatibility problem.