I'm looking for a simple way to implement the standard office custom Task pane TabContainer which looks like this one:
Standard Office TabContainer
(1) is easy to implement
(2) with the TabContainer there is a way to use Icons also - but they don't look so nice like in this one with mouse over effect etc.
(3) I didn't found in the standard TabContainer a setting to enable such a line with a marker
Is this a separate component or does anybody has an example what all is needed to have such a control?
Office has a history of using controls that it doesn't expose to third party devs. The recent files lists for example, are not re-usable, among others.
But maybe they didn't do that this time, maybe they did make it available. They'd probably include it in some release notes, right? But it's not listed in What's new for developers for either Word 2013 or Office 2013 in general.
Okay, maybe they just forgot to include it there? I also took a look through intellisense where I might expect to find it but did not. A bit of googling isn't coming up with anything either.
I don't think this is something you can re-use.
You can of course re-create it. It might be easiest with WPF, but only relatively speaking, It's probably not going to be easy, overall. Also, if you go this route, you need separate and more specific questions than "How do I do this?" Go try to do it, and ask questions related to the roadblocks you run into.
My friend and I are making an iOS app. He has sent me code and I want to edit it, but I want my changes to be in a different color than the rest of the code so he knows where things changed. Is this possible?
I doubt any editor supports this, it might be doable with some kind of plugin, but I doubt that exists either.
Simplest way to do is make a comment on the part you've changed and state your name, but that's a lot of work to use and later to keep track of.
I recommend you to use source control, such as git or mercurial. You and your friend create commits and you can track back each commit, view what changed with that commit and even revert the code.
If you wish to share code with your friend, you'll need to have some kind of remote repository server or service, two most popular that I know of are GitHub and BitBucket. I have used GitHub a lot and it offers great code diff view (difference in code before and after commit).
This service, grouped with a GUI client, which GitHub is offering for free (on OS X and Windows), works really good for team programming projects. If you choose BitBucket, they're offering their own tool, called SourceTree, but it might be a bit intimidating. Good thing about GitHub client is that it works with every service, you just have to manually set up remote for non-GitHub projects.
I know this is not the answer you were looking for, but it is the one you need. Source control is (or should be) used by every professional programming team and knowing how to use it will help you if you ever choose to start a carrer as a programmer. And even as solo programmer, it's a great tool to have, especially when you start making a lot of changes and decide to undo them later on.
I have VS2010 professional and Im working with a large code base that Im unfamiliar with. I want to know what code gets executed when a certain event occurs (namely, when I click a specific button). I know this could easily be done with Intellitrace, but that requires an Ultimate subscription (which is outrageously expensive). Is there any other way I can do this? Ideally without installing anything new (even if its free), but thats not a deal breaker.
You can see what .NET code is executed with Runtime Flow (developed by me, 30-day trial).
I'm trying to trace some legacy code at work, Visual Studio 2003 and .Net 1.1. There are actions done on Keypress and Text change that I know happen but, the Text fields themselves are made dynamically or are a control. I need to find the code that is executed when these things happen. Because of some poor architecture decisions on this piece of software the code is very spaghetti and hard to manually figure out.
What I would like to do is set Visual Studio into a mode where it would break when a specific event is handled regardless of the handler. This way I can get into the code and see through what is being done to make the translations and set variables.
Ultimately I'm trying to trace down when this code accesses the database to do lookups and updates so, allowing to watch for when a database connection happens would also be helpful and achieve much the same thing.
A small ma and pa shop came to me recently with a request to update a vb6 program one of their former part time employees made for them while home from college. On the cd the student provided is both the source code and a installer for the program, which extremely helps. I would like to just give them a new cd with a new installer and the updated source code. My question is, how do I go about creating or if easier updating a installer for a language that entered "Non Supported Stage" back in 2008?
Update:
Just to answer some of the questions, the updates they are asking for are just changing the wording of some labels and changing one control from a textbox to a combobox. They are a ma and pa shop and don't want to pay the cost to have the app re-written to a newer language, even though it has been recommended.
You're going to need a copy of Visual Basic 6 (or Visual Studio 6) which is difficult. If you have an MSDN subscription, I'm quite sure you can download it from their archive, but if not, you might need to buy a copy. Check EBay. Have the ma and pa shop purchase it at their own expense, and they should own it in case they want to make future changes. You can use it on their behalf to do work for them, if you're the only one using it, and just uninstall it when you're done.
Also, if you have a copy of Visual Studio 2005, technically you can "downgrade" to VS6 but you have to call Microsoft and have them send you the install program, and you're not allowed to use VS2005 concurrently with VS6. Yeah, I know...
Ok, so if you've got that far, get the source on your computer and get it under source control. I suggest Mercurial (specifically the TortoiseHg client). I've had lots of luck with it on a VB6 project, and it's free. (Don't use SourceSafe, even if it comes free with VS6!) The distributed nature of the Mercurial repository means you can hand them back a CD with the entire repository on it, and the next poor sap who has to make changes will at least be able to do a diff and know what you did.
As someone else here said, VB6 has a built-in utility for making install programs, but I think you had to have the Enterprise version for that. It's worth finding that out before you get a copy.
Now go ahead and make changes, but be very careful. Remember that you probably don't have any unit tests, so you're likely to break stuff. If you want to be professional about it, there are unit testing frameworks out there for VB6. For instance, vbUnit. Again, I suggest having the customer buy a copy (about $99 for a single developer seat, I think). If the change was anything more than changing the company logo on the splash screen, then this is something I'd invest in. Write tests that cover every module or feature you're going to change. If all the logic is in event handlers in the form itself, carefully remove the code you need to change out into modules that you can write unit tests for. Write the tests to verify the current functionality first.
Then go ahead and make your changes. If you've gone to the trouble of setting up a testing framework, then you might as well use some TDD and write your tests first. Write a test, make sure it fails, write enough code to make it pass, and repeat.
All of this still requires you to have a solid manual test plan to check the functionality at the end. That means you need a solid grasp of what it does. You can pretty much assume that no matter how careful you are, you'll break something you didn't understand. Make sure to give yourself enough time to fix other problems that pop up after you deliver it.
I recommend against re-writing it in .NET unless it's a really simple program with only one form. The effort likely isn't worth it.
Caveat: beware of 3rd party components the original programmer might have used, but not included on the CD. If they used some ActiveX or COM stuff that they purchased from a 3rd party, but they didn't license it to your customer, you might have to end up purchasing it again just to get it to compile.
EDIT:
Based on your extra information, if you're really just changing a couple of controls and wording, then I think you can get away without a unit testing framework. I would definitely use some source control though.
I do remember using the Package and Deployment Wizard, and I agree it sucked. I actually used a 3rd party installer, now that I think about it. However, if the changes are small and the original application used the PDW, I'd probably stick with that.
You Can Convert VB6 projects to .NET.
If you have Visual Studio 2005 or higher...
Or the worse case is re write the code using VB.NET.
Go to this Link.
Convert VB6 - .NET
If I recall correctly, Visual Studio 6 came with a rudimentary wizard for creating an installation program for a VB6 application. So, assuming that you have Visual Studio 6 installed for VB6, there should be an installer wizard that you can use. However, it may have problems deploying the VB6 runtimes on Vista or Win 7 machines. Perhaps another SO guru will have the answer to that one.
You can also use the freeware Inno Setup to create an installer for a VB6 application. More information can be found here. However, it requires more manual effort than what came with Visual Studio.