Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
What I want to be able to accomplish is to silently uninstall any installed anti-virus software (I know it sounds like I will be making a virus but I'm not).
according to Microsoft guidelines every program that properly installs itself makes a registry entry in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall. Usually, the key for the program will be its GUID, or else the name of the program. Within that key will be an entry called UninstallString so I just have to run that string in cmd I guess.
But I have never worked on anything like this before, since I am brainstorming if I will even attempt to do it find out how more experienced developers might approach it.
This is just not going to work out.
Regardless of how pure your motives may be (and I'll admit, I'm still rather suspect, despite your assurances), this is exactly the same thing that other people with impure motives would want to do.
Therefore, any antivirus vendor worth their salt is actively working to prevent this from being possible. In addition, as Matthew points out, Microsoft is working against you, too. In order to make this work, you'll have to figure out a way to skirt around the entire Windows security model.
I suppose you could enter an arms race against them, but they probably have a lot more resources to devote to the problem than you do and stand to gain a whole lot more from solving it. Moreover, the user is the one who stands to lose the most here. Not only is it extremely user-hostile to uninstall programs without their consent, if software vendors are spending their time locked in an arms race, they're not using that time, energy, and effort to improve their software in a meaningful way.
I strongly recommend abandoning the brainstorm before you've wasted too much time. Surely there's a better way to solve whatever task you're working on.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Referring to this question that's already been answer:
"What is the best local-database solution for WPF applications?"
What is currently my best choice of local database for my program? Currently I am using XML that is automatically created on the computer when the user run my executable for the first time or when the XML is missing.
I am perfectly fine on using XMLs, users of my application would not be required to install any software other than my application and I can do exactly with it, but my problem is with searching.
My application includes a database (the XML) of all their songs in their music library, and of course each track has its own information and search through each track is really slow! since it's a music library, one user can have at least 1000 tracks or more and searching through it is really really terrible.
I am familiar on using SQL database, (i don't know the proper term for it) but one for online database, I use XAMPP and read the database on a website on PHP. And i really like it. So..
Basically, I am looking for a good local-database solution, where user's won't to download and install any other software (but I am okay, if i would have to include a certain dll to my exe in other to run), and also one that is lightweight and fast in terms of searching.
Yes, i've read the included related question as many times as i could for me to understand it myself but i hope someone can explain the advantages and disad of each of them.
No, i am not looking for one that needs to have a server or something in order for it to work
Previous suggestion is correct SQLite will be your best option because WPF operates .NET Framework. It also supports ODBC driver as i recall
I was going to just comment but can't quite yet.
I wouldn't say there's necessarily a 'best' in most cases. In general whatever you go with is unlikely to be that bad of a choice..
Having said that, I could suggest SQLite as an option for you. Lightweight, very fast, certainly good for strictly local-database options.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm looking to sell my program I've been working on via year long subscriptions. How do you suggest I do this? Obviously checking DateTime.Now won't work since a user could change his computer time. I thought about having an encrypted number in my program files that counts down from 360 to 0, but if a user simply re-pasted their program files every so often, the timer would never run down.
What do you guys think I should do? I have access to a website and server, I just don't know much about web development besides basic HTML. Would having the program check with a web service to see if the key has expired be the best way? The only thing is that if a user didn't have internet, that would have problems.
Let me know what you guys think :D
Thanks
Every protection can be cracked some more easily that others. Coincidently, those that harder to crack are also most inconvenient for end users and sometimes too expensive. For example you can sell hardware dongle with your subscription.
What many companies settle for is providing a year of "free" updates. Your program evolves as you add new features but these are not available for those whose subscription time has ended. They will be able to use older versions eternally though.
Usually this is a good enough incentive to purchase. But have no doubt, if you program ever becomes even relatively widespread, it WILL BE cracked. That's the reality.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm starting on the second version of a large Solution/Project that I created and was wondering about the best way to go about it. I'll be changing allot of the core code, classes and projects of the solution and that makes want to make this into a separate solution and separate repository.
I've never really started on a version 2 before, so if anybody could give me advice on the best way to go about it I would truly appreciate it.
For the record I am coding in C# and using VS2012.
Thank You
Create a Branch in the repository called Version2 or something (maybe a better code name) and do all the new dev work in that. That way you still have the original Trunk if you need to go back to it. Maybe also create a Tag with the current project that will never change so you basically take a snapshot of it before making any substantial changes.
I usually keep everything in one solution and just evolve the solution. There are several benefits to this:
You refactor your tests along with the project (hope you do have some!)
Keep a tracked version of all the changes in your source control
It's easier to make sure your project is still stable after the refactoring by running test suits or running the executables in debug mode
It is safer to refactor little bits and peaces, than a global re-write, there is a risk you will go a little bit to far with refactoring
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am starting to make my own apps and publishing them. The problem I face is that my apps are mainly for my purposes. What are some problems that you face while in windows? I need some desktop application ideas that are simple but helpful.
Rather than giving you a fish, I will humbly try and teach you how to fish:
Take a blank sheet of paper and write out as clearly as you can the problem that you want to tackle. Clarity is key because clarity of purpose gets your mind focused on what you are really trying to accomplish.
Think of at least 20 ideas and write them down on that once blank paper. Let your mind really flow and give up worrying about whether your ideas are practical or what other people will think about them.
Read over your list and determine which ones actually are good ideas. You might want to put the list away for a while and then take it out the next day to see if you still think those ideas pass whatever test you have for your ideas.
Lather, rinse, repeat.
Note that I don't necessarily know that I have a problem until you show me that I have a problem, and then show me how to fix it. Personally I think computers are still too hard to use, and I'm a programmer. Because my work life is so complex I like software and gadgets that are simple and elegant. MP3 players existed long before the iPod came out, but the iPod was able to get the mix right.
http://hubpages.com/hub/How-to-Come-Up-with-Good-Ideas
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
A couple of months ago I've coded a tiny tool that we needed at work for a specific task, and I've decided to share it on CodePlex. It's written in C# and honestly it's not big deal but since it's the first project I've ever built from scratch in that language and with the goal of opening it from the very beginning, one ends getting sort of emotionally attached to it, I mean you'd wish that the people will actually participate, be it criticism, bug reporting, or what have you.
So my question is, what can I do to actually encourage participation, stimulate curiosity or just recieve more feedback about it?
By the way this is the project I'm talking about: http://www.codeplex.com/winxmlcook/
You should:
Promote it where you think it would be relevant (forums,mailing lists etc.). Try not to spam though - it will create a backlash.
continue to provide updates as to create the appearance of an active project until more people pick it up.
Find project leaders, they are the sort of contributors that encourage others to contribute as well.
Blog about it and link to relevant blogs (creating ping-backs). Also leave comments at relevant blog posts.
Basically, your generic Internet marketing tactics ;)
You first have to acquire users by marketing the tool. Once you have users, that naturally means you'll start getting feedback.
One thing I noticed is your project description doesn't sell the project well. For example, type "winxmlcook" into Google, what gets shown is your project description but it's not likely to get someone to click on it.
I know I sound like a broken record constantly posting this book, but just about everything you could ever need to know about running an open source project is here. In particular, pay attention to these two chapters:
Getting Started
Managing Volunteers