As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Would it be classed as bad practise to have a solution called "Importer" and then have several projects called Importer.[projectname]
Imagine project name is like Importer.Model etc.
Is that good or not?
I want to confirm my thoughts with other developers
Thanks
No, it's not bad practice, as long as you choose appropriate names.
Visual Studio will assume that the project name provides the default namespace, so for a project named Foo.Bar you'll have Foo.Bar as your namespace.
This is useful when you're working on a set of libraries that fit under a parent namespace. For example, you might want to use your company name as the first part of the namespace, and the library name for the latter part, e.g. MyCorp.MailLib, MyCorp.ReportsLib, etc.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I was just wondering when is it recommended to make dll's, when your project is over 1000 lines, 5000lines, more? Also should I make dll's for WPF controls that WinForm project uses?
Or maybe when the project has reached some number of classes?
Thanks in advance
This is entirely a matter of personal opinion, but if you're breaking up into projects due to line count or number of classes, you're doing it wrong. you should have a project (and thus a dll) for every high level logical grouping within your solution. you might have a data project, a domain project... etc. if you're going to be reusing code across solutions, then yes, you'll need a dll for that, or a shared project, or something similar.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
In VS 2010 Web application, I have few design pattern classes Singleton & Factory etc, currently residing in Util Folder. Would it be correct to move them into App_Code folder.
As per the layered architecture what is the recommended place to put them into ?
Thank you for your help.
Different teams have different naming / structure conventions. I have seen Util folder used, Helper folder etc - just check with the team where they would all be happy to house the files.
Also, as you mentioned APP_CODE, are you using Web Project instead of Web Application?
http://msdn.microsoft.com/en-us/library/dd547590.aspx
It's absolutely up to you, or up to the dev-group to decide ho to design layout of these kind of files.
So feel free to pick the most approriate layout for you.
You should structure them in your application as they conform to the model they ultimately represent. There's no pre-defined 'right way' to do it. The system you're modelling is the driving force.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Edit -- I'll try to make my question more to the point
I am working with the DataContractSerializer. I noticed that when I instance the serializer, I can specify the Namespace and the Name. Is there any guidance out there (or maybe a best-practice) to describe when I might want to take control of the name and namespace, and what I might want to use for the values?
I was tempted to use the namespace and class name of the class that I am serializing deserializing. Is that a good or bad practice?
DataContractSerialializer is a contract-based serializer, so forwards compatibility shouldn't a huge problem as long as you are adding - and if you do want to rename, you can hide that by adding the old name via attributes. As such, I would say "keep it simple" - trying to get clever is the cause of many bugs.
Re "What do you think?" (comments) - I think I'd rather use protobuf-net, but I'm somewhat biased :p
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm creating a web-related application and I want to add plugin support to it. But I want the plugin dlls to be restricted from everything except my SaveSettings(), RequestPage() and SendToHost() methods. Any good examples how to do that?
You can require your plugins to implement an interface which contains those three methods. In your code then you would call those methods where it is necessary to apply the plugin functionality.
Of course this will not prevent them from executing code within those methods that is not desirable. This becomes more of a security problem in this case. I can't think of a straightforward way of doing this except to load the plugin assemblies into another AppDomain and set security restrictions on the AppDomain about what they can do. This will also of course complicate how you pass data between your plugin and your code.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I want to generation automatically Resx files for my project, I've heared that there's program which does it.
Can anyone tell me it's name?
The only program I know is Visual Studio. You can easily create your own program by using the ResXResourceWriter class.
As Hans stated, for components such as forms and user controls, you can do this via the "Localizable" property. For other ".resx" files, you can easily create your own localized ".resx" file but it needs to be properly named (you can read up on this - Google for "satellite assemblies" for starters). If your goal is dealing with translations in general however, then unless your app is very small, this approach is difficult, tedious and error-prone (trying to track changed strings on your own for instance, whose existing translations have become obsolete). There are 3rd-party packages that can help you however, and I'm the author of one of them (in the interest of full disclosure). See http://www.hexadigm.com.