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 7 years ago.
Improve this question
For our project needs, I created my own ASP.NET Identity 2.0 Provider with SQLite database, and Entity Framework used in MVC 5.2 application. It's methods are all async. All of the problems with the connection to SQLite DB are resolved (I saw many questions regarding this)
So, my question is very simple:
Does it make sense to share my code with the community on GitHub? Can it be really helpful? What do you think?
Thanks for all answers
Not exactly a technical question, but nevertheless: if I found something like this on GitHub I would totally look into it as I have developed similar features and it would definitely help me compare / improve my work.
So, OK. Here is the link on github where you can see and use if you need to my implementation of ASP.NET Identity 2.0 Membership with SQLite database, and Entity Framework OR/M. I'll also add some more info in readme file of repo about how to use/configure etc. your own implementation and how to skip all problems which can take place when you are working with SQLite and Entity Framework
https://github.com/darklektor/ASP.NET-Identity-SQLite-EntityFramework
Thanks for answers guys
Have a good and nice code :)
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 3 years ago.
Improve this question
I am very new to DOT.net frameworks.
Shouldn't we always update to the latest release?
List Entity framework or identity framework .. all those frameworks ... why do we keep them around? just use the latest ones.
In fact, I am just starting to develop an asp.net website with RestAPIs, login, register, social login...
I wonder what is the best framework version (4.5) to use
From a large company point of view. You can not always technically get the latest version of .NET on your servers that store your applications. For some you have to go through a series of procedures to get everything to the latest so it's not necessarily developers that can trudge through this when you have a separation of duties like developers, system admins, etc. Although it's highly suggested to use the latest and greatest. Every dev/company has their own way of actually getting the most up-to-date versions of pretty much anything.
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 7 years ago.
Improve this question
I just got introduced to log4net and its abilities. For starters I'm currently working on a small project. We need to log errors,warnings etc to a file and also send an email to all developers involved about any Fatal errors. Is log4net an overkill for a small project thats got about 10 classes that require the logging functions? Are there any benefits of using log4net in the long run? We were initially going to just use FileIO manipulations and Mail functions to achieve the same.
The answer on this question is primarily opinion-based, some reasons to use a logging framework from the start:
Standard way of logging
Easy configuration
Small projects will grow, if you do it right from the start, there is no later rework needed
Using a logging framework will not cost you more time than writing your own. It will probably safe time. For example log4net will never crash your program when logging fails. Your own framework might interact with your business logic and gives you unexpected results.
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
Will changing to Oracle from SQL Server require changing any of the existing LINQ or Entity Framework development of a .NET application? The project is currently using SQL Server but there is a recommendation (not a requirement) to use Oracle.
An ORM is a layer to abstract you away from the database. Ideally you won't know what the underlying DB is.
I would get an evaluation copy of Oracle and point your EF at it. The EF is very good at communicating with DBs and I doubt you will have any problem.
Practically you may run into different issues; but until you do some research and ask specific questions about issues this community will be of no help. If you have a data engineer leave it to them to decide on the DBMS and you choose a robust ORM (EF) to abstract you.
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
Is it recommended to use DoctrineMigrationsBundle? Or is it recommended to use Doctrine Migrations at all?
If you are looking for a way to sync your database scripts over multiple database etc it is a good tool, but still not perfect so you will need to check the migrations yourself if you want to be sure.
The doctrine/migrations library doens't have a stable release or alpha so it's still pretty much a young piece of software, but we use it to sync our changes on our development/testing and production databases. It makes it easier to have a central place where you keep and manage your database structure changes.
There is a solution for composer so a stable requirement will not prevent you from using doctrine migrations but it's only a temp solution until we get a reaction from the developers
see: doctrine/migrations#120
So all and all i can say it's a decent piece of software but you shouldn't trust it blindly!
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 want to make a lite facebook version using symfony 1.4. however i had some issues with symfony and memory in the past so :
is it wise to go with symfony ?
what are the server requirements to run it smoothly (cpu, memory ...) ?
Thanks
About the memory it is more or less a question how you define "lite" ;) There are a ton of successful websites using symfony 1.4 (also big ones like for example delicious.com), so I believe that the question of scalability is more about how mature your knowledge is for performance issues.
What are the alternative approaches you have in mind? Writing your own framework? Then my strong advice is to use an existing one instead (does not have to be sf1.4 though), as most work to start implementing the actual application logic is already done for you.
Did you habe a look at Symfony2? As it is a much more modern framework that is quite stable now (as 2.1 with new forms component will be released soon) I would suggest using it ;)