If in a asp.net projects, 10 people are working how to share web.config file among all the 10 people also how to prevent overriding of web.config by many people simultaneously.
Related
This is a query from a beginner wondering about best practice suggestions - I have a system for myself but am wondering what other more experienced people do.
My desired end result is a way to access a number of specified files which are in multiple different places within a working directory.
My specific example is with Django, where my HTML, CSS & JS files are spread in different directories (such as Template & Static). What I'm imagining is a way to quickly access/open all three files, even if they're in different locations - possibly creating a "ProjectFoo" folder, then within that folder are links/shortcuts/aliases to the required files.
I'm currently using the Favorites (https://marketplace.visualstudio.com/items?itemName=kdcro101.favorites) which covers the majority of my uses, and there are also these alternatives:
VSCode-Favorites: https://marketplace.visualstudio.com/items?itemName=howardzuo.vscode-favorites
Project Manager: https://marketplace.visualstudio.com/items?itemName=alefragnani.project-manager
...but am wondering aobut recommendations regarding best practice - what is the usual way people go about this, as it seems (to me at least) that it might be a common workflow issue.
Thanks!
Rich
I'm looking to break up an app into multiple tiers and am curious how others have tackled this before.
Have you simply created a folder for the business and data layers or have you broken up the app into multiple targets (one for BusinessEntities, BusinessLogic and DataLayer)?
I go with folders. I have the structure of my folders reflected in the organization of the classes in Xcode, too. This works very well, I can collapse the stuff I don't need and it is out of the way.
The scope of this is that we have three main projects. Some of the source files are shared between the projects. There are nearly 3 million lines of code (not including comments or spaces) that has grown over 20 years. We currently use Source Safe for our version tracking. But this is starting to fail us as we expand not only our products but also by how many developers we have playing in different modules that are shared. An example of a shared file would be a template class. The code is solid and is used in many projects. It is a single file so it is just shared between the projects. Now 20 years later that one file has grown to over 1000 files (Yes I would love to refactor and make libraries, not happening). Does Mercurial support the same kind of concept in some way?
Thanks
Mark
Mercurial subrepos may be what you're looking for, if I'm reading your question correctly.
I have a scenario where I am asking consultants to deploy 2 applications. A console application and an IIS web service application. Both apps form part of the solution.
I haven't created an easy to use installer, but was wondering if there is an open source config editor that I can ship with my app that can read in "only certain" values and allow the consultant to change these values.
This would be much less hassle than asking the consultant to open up web.config or app.config - because the configuration is pretty complex for a non technical person, and they're overwhelmed by all the XML.
I guess as a programming question, this would be a question relating to deployment.
What exactly are the sections which you want the developers to read ? I would refer you to this question Can a web.config read from an external xml file?. You can keep part of your web/app.configs externally and read from them.
more reference:http://blog.andreloker.de/post/2008/06/Keep-your-config-clean-with-external-config-files.aspx
I do alot of bugfixing and implementing new features for several different customers. These customers all report their bugs, change requests and new feature request into our Trac system.
Sometimes these requests result in me creating some SQL change scripts, sometimes there are Excel documents or Access databases with testdata, Word documents from the customer and so on. Alot of files that are used to fix one ticket and then can be deletede when the ticket is closed.
I usualy do this by creating folders in the filesystem like this: /customerXX/TicketNNNNN and then just dumping everything in there.
How do you organize your workfiles? Have you found some fantastic tool to do this?
I would say for scripts or files that are related to a particular ticket, the best thing to do would be to attach the file to that ticket in your issue tracking software - almost all issue trackers that I've worked with will allow you to do this. That way, you can look back and a) see exactly what you did in case something goes wrong, or b) do exactly the same thing if the issue comes up again later. That's almost certainly the best place to keep files with extra info from the customer, too (or at least the first place most people will look).
For frequently re-used scripts that aren't specific to a particular ticket, I would create a scripts/ or bin/ directory in the associated project, and keep them in there.
I also have a small handful of useful files that I keep in src/misc/ off my home directory, with things like SQL queries to get readable "explain" output out of Oracle and such, that aren't specific to any particular project. The number of these is small enough that subdirectories aren't necessary, though - I suspect if you ended up with a large number of these files, many of them could/should be moved to specific projects or your issue tracking system.
JIRA has been quite helpful for this at my site. It supports issue tracking, file attachments,and you can easily customize and categorize your projects and issues.
I use Fogbugz and I add all file to the case. I believe that no matter what application you use, The important is to keep this files for future references. If your bug-tracking tool does not let you attach file then add the files to the version control.
We use CaWeb4 and find it very easy to use for our bug tracking.