Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 1 of 5

Business Logic Toolkit is a set of components to simplify .NET application development. BLToolkit is provided as source code that you can use "as is" or customize for your applications. It is written in C# and compatible with .NET Frameworks 3.5 and 4.0, Silverlight 4, and Mono.

5.0
 
  0 reviews  |  4 users  |  171,960 lines of code  |  22 current contributors  |  Analyzed 7 days ago
 
 

Geospatial Services Implementation Kit eases the development of OGC Web Services in .NET.

0
 
  0 reviews  |  2 users  |  400,329 lines of code  |  1 current contributor  |  Analyzed 3 days ago
 
 

.Net client for Embed.ly

0
 
  0 reviews  |  1 user  |  2,272 lines of code  |  1 current contributor  |  Analyzed 6 days ago
 
 

Ximura is a extensible information management system designed using C# 3.0. Ximura is intended to shorten the development time for building large complex system, by providing a development framework built around a reusable component architecture. Ximura is CLS compliant and works under the ... [More] MONO framework for use on Linux based machines, as well as a standard Window's based environment. [Less]

5.0
 
  0 reviews  |  1 user  |  181,428 lines of code  |  1 current contributor  |  Analyzed 5 days ago
 
 

JsonFx.NET ExamplesExample projects built using JsonFx.NET, the JSON-savvy Ajax Framework for ASP.NET. For environment setup help, see: http://help.jsonfx.net/instructions For ASP.NET MVC, Web Application and Web Site Visual Studio Project Templates, see: http://jsonfx.googlecode.com ... [More] "UIToolkit"JsonFx.NET (JBST, JSON-RPC) C# / ASP.NET / Visual Studio 2005 jQuery 1.3.2 UIToolkit shows how to build reusable control libraries which allow sharing of JBST client-side templates, scripts, and stylesheets among many projects. The UIToolkit is an example implementation of a full-featured TreeView control, flexible modal dialog controls, loading indicator and buttons with various states. The UI controls and affiliated parts are compiled into a redistributable Assembly which is also available for download. "OpenID Dialog"JsonFx.NET (JBST, JSON-RPC) C# / ASP.NET / Visual Studio 2008 DotNetOpenAuth jQuery 1.3.2 The third example is an OpenID library which can be easily added to another to provide a clean UI for authenticating via various OpenID providers. This project demonstrates how JsonFx easily allows UI components to be created as reusable libraries. Scripts, StyleSheets, and JBST UI controls may all be embedded into Assemblies and easily shared among multiple projects. (still in development) "CalendarApp"JsonFx.NET (JBST, JSON-RPC) C# / ASP.NET MVC / Visual Studio 2008 LINQ-to-SQL / C# 3.0 Anonymous Objects Date.js jQuery 1.3.2 The second example application is a multi-view, shared calendar app. Users can add events and view a shared calendar in the spirit of Google Calendar or Apple Mobile Me. CalendarApp shows integration of JsonFx within an ASP.NET MVC application. Each year, month or day view of the calendar has a unique, user-friendly URL. (still in development) "MusicApp"JsonFx.NET (JBST, JSON-RPC) C# / ASP.NET WebForms / Visual Studio 2008 LINQ-to-SQL / C# 3.0 Anonymous Objects jQuery 1.3.2 The first example project in this series is an application that allows inline editing of music bands and their members. Users can edit artists and the members directly inline, dynamically switch between views, and navigate between genres and artists. As an extreme example of Ajax, the "one page" application, demonstrates the power of JsonFx.NET client-side templating (JBST) and Ajax services (JSON-RPC) in combination with jQuery and LINQ. The UI is wired up using the freedom of pure JavaScript and standards compliant markup/CSS. Data is requested via Ajax and client-side templates are dynamically bound in the browser which allows grid column sorting and change of view-type without re-requesting the bound data. This project uses LINQ-to-SQL as a simple DAL. For client-server communication, the JSON-RPC service bi-directionally serializes LINQ-to-SQL entities and unidirectionally serializes C# 3.0 Anonymous Objects as DTOs. [Less]

0
 
  0 reviews  |  1 user  |  70,461 lines of code  |  0 current contributors  |  Analyzed 5 days ago
 
 

Linqdbg is a .Net library intended to query windbg (cdb, actually) using LINQ in an external program or in a REPL interface. It provides a gentle, strongly-typed alternative to windbg scripting with some of the most commonly used sos/sosex commands supported. linqdbg builds upon the ideas behind ... [More] the excellent powerdbg (http://www.codeplex.com/powerdbg) from which it borrows its main mechanism for windbg/cdb interaction. Right now, it's in a very, very preliminary state. [Less]

5.0
 
  0 reviews  |  1 user  |  806 lines of code  |  0 current contributors  |  Analyzed about 2 years ago
 
 

Linq to ExcelUse LINQ to retrieve data from Excel spreadsheets! View the introduction videoBasic Examplevar repo = new ExcelQueryFactory(); repo.FileName = "pathToExcelFile"; var peopleWithSiblings = from p in repo.Worksheet() where p.Siblings > 0 ... [More] select p;Linq to Excel assumes the property names on the Person class match the column names in the worksheet named "Sheet1". What if your class property names don't match the column names or the spreadsheet you're using is not named Sheet1? Then see the CustomizingLinqToExcel page. Go to the GettingStarted page for a tutorial on implementing Linq to Excel in your project. Need help? Send questions to the Discussion Group [Less]

0
 
  0 reviews  |  1 user  |  68,734 lines of code  |  3 current contributors  |  Analyzed 14 days ago
 
 

PLINQO, which stands for Professional LINQ to Objects, is a collection of CodeSmith templates that are meant to replace and extend the LINQ to SQL designers that are included with Visual Studio 2008. Video TutorialsPLINQO Part 1 - The Quick Start PLINQO Part 2 - Feature Overview FeaturesTemplates ... [More] for both C# and VB Many features can be turned on or off depending on your needs Generates a fully funtional UI and data layer in under 60 seconds Dynamic Data UI Meta Data classes for customizing Entity attributes. Generate or update a LINQ to SQL dbml file from a database schema. Includes all tables, stored procedures, functions, and views with the ability to exclude objects based on regex patterns. Ability to automatically remove object prefix and suffixes (ie. tbl and usp). Dbml file can still be customized with the normal Visual Studio 2008 designer. Dbml file can be refreshed based on the current database schema without losing customizations. (See Safe Attributes) Generation of the LINQ to SQL DataContext class. Generates ADO.Net Data Services Generation of the LINQ to SQL entity classes. Generates one file per entity instead of one massive file. Generates partial classes where custom code can be written and won't be overwritten. Generated entity files are added to the project as code behind files to their corresponding custom entity files. Adds customizable business rules engine to enforce entity validation, business and security rules. Generation of entity manager classes. Provides access to common queries based on primary keys, foreign keys, and indexes. Common queries are exposed as IQueryable so they can be extended. Generation of Query classes All templates can be customized to meet your needs. Reasons to use PLINQORemove the designer black box and allow for customization of the ouput while still retaining the ability to use the .dbml designer to make customizations inside of Visual Studio. Ability to easily generate your entire .dbml file for a database and then the ability to regenerate that .dbml file as the schema changes. The regeneration preserves any customizations you may have made such as entity, property and relationship names. With the designer, if you make a database change, you need to drop the entity and re-add it to get any new columns or data type changes, which would cause you to lose any customizations you may have made. Also, using the templates allows you to exclude unwanted tables, stored procedures and views using filter expressions and automatically strip / clean entity and property names of things like prefixes and suffixes that your database schema may be using (ie. tbl_Customer to Customer). A business rules engine that allows you to enforce things like property length rules, required field rules, regex data validation rules as well as several other built in rules including authorization rules. The SubmitChanges method on the data context object will automatically run the rules against any entities in your change set. If all rules are not met, a BrokenRulesException will be thrown that contains a list of the broken rules. A manager class is generated for each entity that encapsulates all actions taken on an entity. Known common actions like retrieving entities by primary key, indexes, and foreign keys are generated. Any custom actions can be added and will be preserved during regeneration. While LINQ makes it easy to sprinkle your data access logic throughout your entire application, we still believe its poor design to do so and that is why we have included the manager classes. A fully functional Dynamic Data UI on top of Linq to SQL. More InformationCodeProject article: PLINQO - Supercharge LINQ to SQL Paul's Blog [Less]

5.0
 
  0 reviews  |  1 user  |  0 current contributors  |  Analyzed 7 days ago
 
 

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.

0
 
  0 reviews  |  1 user  |  6,131 lines of code  |  1 current contributor  |  Analyzed 5 days ago
 
 

A project that provides a base framework for applying the specification pattern via a Linq implementation.

0
 
  0 reviews  |  0 users  |  848 lines of code  |  0 current contributors  |  Analyzed 10 days ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.