The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I typically save a file in the working directory, which allows the user to set up different shortcuts with different preferences if they want, and it makes the app portable as nothing is stored in system folders (or the registry etc) so you can put it on a USB stick. I put default configuration settings into the app as a resource so I can use the same reader to load it.
My application is a bit different. We run a printing press and related equipment. In that case, there aren't any 'user-specific' data to be persisted. At one time we would have used HKEY_LOCAL_MACHINE in the registry and called it a day, or stored a file with our application. Under Win7, none of that works. Our current solution is a group of XML files stored in the folder returned by SHGetKnownFolderPath(FOLDERID_ProgramData)[^].
I keep waiting for some moron to suggest we store settings data in the 'cloud' even though our machines never have an Internet connection...
It depends. In some applications it makes sense to use an XML file; in others, I use the registry; in others a database. In terms of what to save there: again, that depends on the applications. In some applications, form state is an integral part of how a document is displayed; in others it's unimportant. The same is true of behavioural settings. For Client/Server stuff, there usually ends up being a mix of techniques: things you want to persist across multiple installations of a product (by user) get stored in the database; stuff which has more to do with how the application looks on the screen of a specific machine get stored in the registry. I think it's all about common sense -- ask yourself questions like, "How annoying would it be if [this setting] did[n't] persist across different installation instances?".
I was asked this question at work. My first thought? How the hell do I know? I can't be done just like that. I would require to rewrite whole application. How much time it takes to make application for medium-sized company? 2? 5? After 10 it usually still under work and people are thinking about rewrite it in some other/better technology.
Worse is that I don't even know what is doing. There are now complete documentation, I saw it once and I don't have complete access to code. So how much time it would take? To hell with that. Whatever I will say it will be wrong anyway; nobody can predict that.
Give me 5 people and 2 years, I could care to try.
Whatever I will say it will be wrong anyway; nobody can predict that.
That is a case for project-management. It should be project, you could gather the data, look at the code and the documentation.
With all functional requirements, complete UML models and experiences from the development you can predict the time. Therefore is project-management.
This is a problem. There are almost no documentation. At least no technical. Just few describing functional behavior. It is not the worse thing. I really can't say what this application is for. Jeez! This is madness!
No wonder why companies raise and fall constantly. This is no way to do business. If you are mistaken with prediction such as this and you have to pay to do development for someone because contract made you to finish this...
But you have to tell something. One thing is good that this will be not my fault when something will goes down...
Yes, you are totally right! I worked for a lot of IT-companies and the most did it wrong. My actual employer is different. We are project driven and we have a complete project management. It's so much easier, when you habe time to initiate a preproject, gathering all requirements, analyse them and your prediction is based on facts.
You can't really convert Web Forms to MVC, you'd be more into starting again but using the functional behaviour of the old system as your requirements. Web Forms is notorious for tangling up UI, business logic and database access code, so unless yours has been coded by particularly careful people you won't even easily be able to pull out the back end part.
Yep. I know that.
You know that.
Management does not know that.
As for good code in business applications... it is like polar bears: you heard of them, you saw the foto, maybe even saw one in ZOO but it is not living in your neighborhood.
So actually you have to start over again.
I use Opera as a last resort browser when it seems that all the anti-ad extensions & add-ons won't allow the website to work properly. Since I have none of that on Opera, like I do for Firefox especially, and to some extent Chrome, it always seems to work properly. And while I don't mind the ads on the specific page I go to, I do get bugged by the ads that are displayed on the initial tab page in Opera - something that seems to be optimized for my location as I get ads for the USA when there, and ads for Russia when I am there.