Promact guidelines issues

Promact / guidelines

A collection of guidelines for Development and Best Practices guide

MIT License

1 stars 3 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Merging Jekyll branch to Master

#18 ShreyashPromact closed 4 years ago
0
Added android programming guideline

#17 ShreyashPromact closed 6 years ago
0
exception handling best practices

#16 chintans opened 8 years ago
0
Change behavior in side bar from Mouse hover to mouse click.

#15 chintans closed 8 years ago
0
Which concepts should we put in EntityFramework section?

#14 rushi216 opened 8 years ago
2
design front end of this repository

#13 chintans opened 8 years ago
6
Estimation format

#12 chintans opened 8 years ago
0
Explanation of Project structure

#11 chintans closed 8 years ago
4
Use RegisterAssemblyTypes for registering Repository, Libs, Utils etc (which follows same name suffix)

#10 rushi216 opened 8 years ago
0
Indexing best practices

#9 chintans opened 8 years ago
0
Define OOPs concept for general user and how to use it in actual programming

#8 chintans opened 8 years ago
0
Git best practice

#7 ashikkalavadiya opened 8 years ago
0
Avoid too many parameters

#6 RiyaShah closed 8 years ago
3
Naming conventions

#5 rushi216 closed 8 years ago
3
reference material for further reading

#4 chintans opened 8 years ago
0
Any function/method should do only one job. Do not combine more than one job in a single method, even if those jobs are very small.

#3 RiyaShah opened 8 years ago
7
Declare all member variables/properties at the top of a class, with static variables at the very top

#2 RiyaShah closed 8 years ago
3
Provide an example explaining OWIN to beginner

#1 chintans opened 8 years ago
0