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
Is it good practice to name preface project names within a solution like so?
CompanyName.P01
CompanyName.P02
CompanyName.P03
Or is it safer to use a convention like this?
CompanyName_P01
CompanyName_P02
CompanyName_P03
To me, the [.] separator looks nicer, and provides intellisense, but is there any caveat to using it?
Most of the solutions I came across follow the following convention:
CompanyName.SolutionName.LayerName
So basically in a company named COMP and a Project Named StackOverflow, you would end up with a project that looks like this:
COMP.StackOverflow.Business
COMP.StackOverflow.Data
COMP.StackOverflow.Web
COMP.StackOverflow.Core
This allows you to easily manage the generated assembly, so if you need to create a common library to be used in your company. You would name it:
COMP.SomeFrameworkName;
That would easily seperate your company's (or Team's) Dlls from external Dlls and Nuget Packages.
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 5 years ago.
Improve this question
I've read Clean Code by R.C. Martin and I'm trying to adopt his suggestions about clean code as broadly as possible.
But I'm not sure how to name related classes.
Let's say I have a class named TreeDirectoryList.
I want to cut implementation of this class into many smaller classes.
Let's say I'll create a class named ParentIndexStack.
ParentIndexStack will implement functionality very dependent on TreeDirectoryList, so it's very not probable that this implementation of ParentIndexStack will be useful with any other class in the future.
But the name of ParentIndexStack is very generic, it's possible, that I'll need another class with the same name, within the same project.
So I thought I'll name ParentIndexStack more precise, like TDLParentIndexStack (prefix TDL is from TreeDirectoryList).
Would it be correct ?
I'll end with many classes starting with TDLxxxxx.
One option is to put that set of classes in their own namespace. Then you can have simple, concise names that still communicate the full meaning of the class through the namespace context.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have xgeno.mvc.utilities dll in my project references. I want to edit one of the method of this dll.
Can I do this?
You have to use a decompiler for this which has many variants on the web (there's google) and then make the modifications on the decomplied files and then compile it again and then point that newly compiled dll to your project
You need something like .NET Reflector, but since it is not free, you will probably want to look for free alternatives. See Here some discussion wich can help in the search.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
So I've downloaded a source code from projectcode.com and it's name is BigInteger.cs and it contains codes needed for working with integers beyond UInt64. How can I use it in my projects?And please be noob-friendly in your answers, I've started learning 3 days ago ...
Thanks for your help in advance.
Ideally, you'd want to use BigInteter class from .Net Framework. If you need decimal precision as well, there is no standard BigDecimal available, but a few workarounds can be found here.
If you still want to use that project, you have several options:
Download an assembly file and reference it in your project
Download source code, build it, reference output assembly in your project
Download only the needed file, provided it is self-contained, add it to your project and use it
In any case make sure to follow the license terms.
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
I'm being tasked with making a modular program that uses external, easy to edit files to dictate if certain elements are shown, what classes are used, etc.
Using C# and Visual Studio 2008, what type of file should I use? I was suggested .ini, but there is also talk of using .xml for it?
Which file would be best, and is there a built-in C# method of working with those files?
There's a heap of different ways for achieving different things. You could for example use an appSetting in an app.config file to turn features on and off. If you wanted to change classes or services that are used, then you could use DI/IoC with something like Castle Windsor and configure that in code and or xml.
If you can be more specific with what you want to achieve, and some examples in code, you can probably get some better answers.
you can use custom sections in your config files.
Config files are xml, well known files in .net context.
See example here: http://msdn.microsoft.com/en-us/library/vstudio/2tw134k3(v=vs.100).aspx
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
New to WPF and XAML. What does sap and sapv name spaces in xaml files mean and how do I resolve them? Thanks.
This should probably be a comment, but won't fit.
It sounds like you may well be referencing Workflow dlls without having added the relevant references (it's a slight stretch based on your Workflow tag).
sap and sapv often reference the System.Activities.Presentation.dll, which you may not have added to your project.
e.g:
xmlns:sap="clr-namespace:System.Activities.Presentation;assembly=System.Activities.Presentation"
xmlns:sapv="clr-namespace:System.Activities.Presentation.View;assembly=System.Activities.Presentation"
Examples and advice here (depending on what it is you're doing): http://msdn.microsoft.com/en-us/library/dd489419.aspx