This project is read-only.

Northwind.NET v.2.1 (.NET Framework 4.0)

Rating: No reviews yet
Downloads: 11268
Change Set: 57241
Released: Feb 4, 2011
Updated: Feb 21, 2012 by ShamilS
Dev status: Stable Help Icon

Recommended Download

Source Code
source code, 39174K, uploaded Feb 4, 2011 - 8056 downloads

Other Available Downloads

application, 5565K, uploaded Feb 4, 2011 - 1757 downloads
Application NorthwindNET DB MS SQL 2008 R2 Backup
application, 652K, uploaded Feb 6, 2012 - 889 downloads
Application My N-Tier Sample Walk-Through (with MS Access backend DB)
application, 1786K, uploaded Feb 21, 2012 - 566 downloads

Release Notes

Northwind.NET v.2.1 is a port of Northwind.NET 2.0 to .NET Framework 4.0.
This new version has also got significant code refactoring comparing to v.2.0 including (but not limited to) changing ADO.NET DAL layer to ADO.NET Entity Framework DAL .
The main solution file is called Northwind.NET.VS2010.sln.
Is builds two front-end applications:

- 1) Northwind.NET.EDM.FE.exe - WinForms-based FE with EDM backend;
- 2) Northwind.NET.WPF.FE.exe - WPF front-end hosting WinForms controls from the same user controls class library used in the first front-end.

There are a few other solutions released:

- 3) Northwind.NET.MSAccess.sln - it has:
a) Northwind.NET.FE.1.1.csproj - MS Access back-end based WinForms/ADO.NET port to .NET Framework 4.0;
b) Northwind.ASP.NET.MSAccess.Reporting.RDLC. - sample MS Reporviewer 10.0 ASP.NET web site

After you'll unzip or SVN-checkout source code of this release at your environment you'll have to:

- restore Northwind.NET database - its backup is in .\zzzArchive\20101226 subfolder and then
- edit app.config files in .\Northwind.NET.EDM.FE and .\Northwind.NET.WPF.FE subfolder to have connection strings adjusted to your data context.

If you wanted to try some unit tests then you'll have to edit app.config file in .\Northwind.NET.Testing.Console subfolder.

.\zzzArchive\20100128 subfolder has zipped MS Access back-end.

Within this project phase there was also an attempt to make "quick&dirty" XBAP application using WPF port mentioned above.
But that attempt failed - below (see P.S.) is the first part of runtime exception stack.
Looking for solution of that issue.
All and every hints, tips and tricks how to make that "quick&dirty" XBAP port workable (if possible at all) are very welcome.

Thank you.

-- Shamil


Startup URI: E:\Projects\SMS\Northwind\Bin\Northwind.NET.XBAP.FE.xbap
Application Identity: file:///E:/Projects/SMS/Northwind/Bin/Northwind.NET.XBAP.FE.xbap#Northwind.NET.XBAP.FE.xbap, Version=,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil/Northwind.NET.XBAP.FE.exe, Version=,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil, type=win32

'The invocation of the constructor on type 'System.Windows.Forms.Integration.WindowsFormsHost' that matches the specified binding constraints threw an exception.' Line number '14' and line position '14'.
---> System.MethodAccessException:
Attempt by security transparent method 'System.Xaml.Schema.XamlTypeInvoker.CreateInstance(System.Object[])' to access security critical method 'System.Windows.Forms.Integration.WindowsFormsHost..ctor()' failed.

Assembly 'System.Xaml, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089' is marked with the AllowPartiallyTrustedCallersAttribute, and uses the level 2 security transparency model. Level 2 transparency causes all methods in AllowPartiallyTrustedCallers assemblies to become security transparent by default, which may be the cause of this exception.
---> System.Security.SecurityException: Request failed.

Reviews for this release

No reviews yet for this release. (Previous release: 5 stars out of five with 1 rating and 1 review)