Projects tagged ‘linq’ and ‘sql’

Linq provider for MySQL, Oracle, SQL Server, PostgreSQL, SQLite, Ingres and Firebird

A SQL to LINQ translator that will help the development community to adopt the new expression language using a user friendly integrated tool for Visual Studio 2008.

A trouble-ticket/help desk solution written by those who are tired of the bloated 'Industry Standard' systems. This is a free, open-source, scalable, tested solution that is already in use by a ... [More] government agency with thousands of users. Windows and Active Directory integrated. [Less]

IQToolkit is essential if you are building your own LINQ IQueryable provider. It contains common tools and source code you can apply to your own project.

MANAZRA is a web application developed in ASP.NET MVC. It allows users to post articles and have interactive discussions on them.

LINQ to SQL Entity Base is a simple base class that is primarily designed to support LINQ to SQL in a disconnected way, which is one of the shortcomings of the LINQ to SQL technology at the present ... [More] time. This is highly useful in an n-Tier, distributed or ASP.NET environment where disconnected functionality is relavent. [Less]

A utility of sqlce 3.5 management. Support Import data from oledb,sql server ,mysql....etc..

Contains all of the source code to AlexDresko.com. This site is not yet hosted, mostly because it's not ready yet. Still, posting the source code to my site is something I've always wanted to do. So ... [More] , those who are interested can watch it grow with me. Current features * Built using ((ASP.MVC || MVC.NET) WITH the TDD part) * LinqToSQL used for data access * Dynamic Data Services (DDS) used for quick and easy data manipulation * Flickr.NET used to display recent/important images on the home page (feed length is configurable via DDS) * RSS Toolkit v2 used to consume and aggregate multiple RSS feeds into one main feed on the homepage. (feed length is configurable via DDS) * MasterPage built with design from an open source web design (http://www.oswd.org) * Automated solution packaging allows the entire solution to be quicky and easily packaged into a version-named zip file. The zip file contains only the files that are marked for inclusion in the .sln file. I created this "feature" so I can more efficiently deliver new builds to the community, but the technique is applicable to any VS solution. Peep the issue tracker for more information. [Less]

BlogEngine.Net's built-in DB access uses generalized DbProvider functionality. This project accepts a dependency on SQL Server in order to take advantage of options specific to LINQ to SQL. Mutliple ... [More] blogs on a single installation and database now supported. [Less]

A Blog Engine based on ASP.NET MVC framework. It seems several of these projects have begun, with little or no action. I would like to begin this project and make sure that it stays alive by ... [More] frequent code posting (every 2 or 3 weeks) and posting to discussions (at least once a week). Also we will try to respond to all who inquire about participating in the project. I was hoping to find a more inventive name, but this is all I came up with so far. Perhaps we can change it later. We will most likely follow along some guidelines such as the Rob Conery MVC storefront screencasts. The engine should be simple, yet designed powerfully enough from the beginning to handle the requirements. The goals will be as follows: 1. Utilize built-in features such as ASP.NET Membership 2. Utilize other open-source frameworks such as the ASP.NET Membership MVC starter kit. 4. Provide for multiple blogs per installation 5. Provider for multiple authors per blog 6. Use AJAX where appropriate 7. Most likely use JQuery for AJAX and other client-side effects 8. Try to avoid "heavy" implementation such as excessive http handlers, etc. 9. Not try to be all things. For example, this will be a blog engine, not a CMS. 10. Allow for easy integration into existing websites and with other products such as a CMS. 11. As much as possible use TDD though with a pragmatic approach. 12. Utilize Design patterns where appropriate 13. Have a simple skinning/theming architecture, but one that makes most modifications by way of CSS and have a theming architecture that plays nicely with existing websites and doesn't "take over" everything. 14. Provide a layered architecture whereby users may make use of an API if they desire to include some features in their own views for example if they are using web forms. 15. Use SQL Server for the data store 16. Use a repository pattern for data access and testing 17. Utilize LinqToSQL or perhaps the Entity Framework Other ideas?... [Less]