Suggested Resources for .NET Developers

  •        61

Suggested Resources is a proof of concept in aggregation of online content inside Visual Studio and analysis of a developers work, in order to suggest applicable resources to the user. Using the tool is like having a programming pair that knows about anything posted to the net.

http://suggestedresources.codeplex.com/

Tags
Implementation
License
Platform

   




Related Projects

pulibrary-docs - Best practices documentation for collaboration with http:/github.com/pulibrary.


Best practices documentation for collaboration with http:/github.com/pulibrary.

SQL Server Stored Procedure best practices


This SQL Server stored procedure best practice guide contains documentations of best practices and helper tools to enhance further match with the best practices.

Trusted-Advisor-Tools - The sample functions provided help to automate AWS Trusted Advisor best practices using Amazon Cloudwatch events and AWS Lambda


AWS Trusted Advisor provides real time guidance to help users provision their resources following AWS best practices. You can now create configurable, rule-based events for automated actions based on AWS Trusted Advisor’s library of best-practice checks using Amazon CloudWatch Events. The sample functions provided help to automate Trusted Advisor best practices using Amazon Cloudwatch events and AWS Lambda.Trusted Advisor Tools is licensed under the Apache 2.0 License.

wptheme-xhtml-KITCHEN-SINK


WordPress theme I originally created for developing custom client themes. Draws heavily on TwentyTen (and some of the best practices I saw elsewhere) as well as utilizing my long time markup/css/js practices I now call ZUI. This was a standalone base theme and is no longer used but saved for old clients and nostalgia. Documentation is available on my site. This is kind of a mess really because it never got fully updated with the stuff I kept back porting from client projects so some stuff is kin

node-require-s--best-practices - Some best practices / conventions when using Node's `require()`


Some best practices / conventions when using Node's `require()`



Node.js-Best-Practices


This is a list of best practices for writing robust Node.js code. It is inspired by other guilds such as [Felix Geisendörfer's Node Style Guide ](https://github.com/felixge/node-style-guide) and what is popular within the community.These best practices should relate to performance and functional differences between various types of coding. They should focus heavily on giving detailed written explanations and coding examples when possible. They should not be a list of style preferences. Lists lik

docker-best-practices - docker best practices/ proof-of-concepts/ ...


docker-best-practices=====================```local-workflow approach-data-container + very granular + only re-build what changed + devop takes care about nginx and config, dev takes care about www-data + allows different config for dev/prod (ie ssl certs) - feels complex with too much overhead - config/data/app can run out of sync (in production) approach-inheritance + only re-build what changed (at least not the base image!) + config/data/app won't run out of sync +

module-best-practices - :books: some best practices for JS modules


:books: some best practices for JS modules

django-best-practices - Django best practices by ZooM Xerus Team


Django best practices by ZooM Xerus Team

best-practices - Where I collect any best practices I stumble across in my travels


Where I collect any best practices I stumble across in my travels

Ruby-Best-Practices-Trials - me reading through Ruby Best Practices and trying stuff out


me reading through Ruby Best Practices and trying stuff out

best-practices - A wiki of best practices for programming Java


A wiki of best practices for programming Java

ansible-best-practices - This is my working example of Ansible best practices


This is my working example of Ansible best practices