Northwind.NET

Source code checked in, #70298

Project Collection Service Accounts — Mon, 01 Oct 2012 21:36:45 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #70297

Project Collection Service Accounts — Mon, 01 Oct 2012 21:31:58 GMT

Checked in by server upgrade

Released: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

Tue, 21 Feb 2012 15:27:43 GMT

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.10.0.0.0/ - 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

P.S.

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=1.0.0.0,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil/Northwind.NET.XBAP.FE.exe, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil, type=win32

System.Windows.Markup.XamlParseException:
'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=4.0.0.0, 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.

Updated Release: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

ShamilS — Tue, 21 Feb 2012 15:27:43 GMT

Updated Release: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

ShamilS — Tue, 21 Feb 2012 15:26:08 GMT

Updated Release: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

ShamilS — Mon, 06 Feb 2012 15:57:25 GMT

Released: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

Mon, 06 Feb 2012 15:57:25 GMT

Released: Northwind.NET v.2.0 (Feb 04, 2011)

Mon, 06 Feb 2012 15:42:33 GMT

This version additionally to Northwind.NET v.1.0 has:

- sample WinForms project with MS Access .mdb backend;
- sample MS ReportViewer Reporting ASP.NET web site with MS Access .mdb as backend. This sample ASP.NET application is currently running here: http://shamils-4.hosting.parking.ru/nw/

MS Access .mdb backend was prepared by mainly manual downgrading of MS SQL 2005 backend database from Northwind.NET v.1.0.

In the new releases we will keep using MS SQL 2005 database as main backend with this v.1.2 MS Access backend database used in some use-case sample scenarious...

This version requires .NET Framework 3.5, MS ReportViewer Control 2008 and JET 4.0 installed on target system.

1-MAY-09: Added MSAccessWebService.zip - a "food for thought" to "brain-storm" in what directions attached sample can be developed - what useful applications for MS Access developers and power-users can be prepared using this technique of wrapping Web Services (and just .NET Framework (application) classes) into simple VBA-callable COM-wrappers.

6-JUN-06: Added NWNetSLApp.zip - simple SilverLight solution consuming ADO.NET Data Service to present Shippers data. It was put here just for starters to invite participating in SCRUM Northwind.NET.SilverLight. Silverlight app from this solution is currently published here:
http://shamils-4.hosting.parking.ru/sl/NWNetSLAppTestPage.aspx and it consumes ADO.NET Data Service currently published here http://shamils-4.hosting.parking.ru/NorthwindNetDataService/NWNetDS.svc. If you will try to make this application and ADO.NET Data Service build and run locally please carefully read this article "Using Silverlight 2 With ADO.NET Data Services" http://msdn.microsoft.com/en-us/magazine/dd569758.aspx as well as this blog entry "Hosted ADO.NET Data Services & Silverlight" http://dvanderboom.wordpress.com/2009/01/07/hosted-adonet-data-services-silverlight/. Please also note that attached archive doesn't contain NorthwindNET MS SQL 2005 sample database - you can find this database backup in another attachment to this post NorthWindNETDatabaseBackup.zip

23-JUL-09

Added:

- SPJ_SQL2005.zip - C.J.Date sample database (prepared here);
- SPJWinFormsForEF_VS2008.zip - VS2008 sample project to demonstrate WinForms and MS ReportViewer reports bound to ADO.NET Entity Framework object datasources;
- SPJWinFormsForEF_Executables.zip - just executables and sample database for the above sample project.

29-DEC-10

Created a new set of projects to support working with ADO.NET Entity Framework for .NET Framework 4.0.
Released NorthwindNET40SampleAppsSetup.zip - sample executables setup
and
NorthwindNET40_Sources.zip - all the sources.
For the latter set of sources you have to edit three app.config files:

Northwind.NET.EDM.FE\App.Config
Northwind.NET.Model\App.Config
Northwind.NET.Testing.Console\App.Config

to set Data Source attribute of connection strings to your MS SQL Server environment.

Updated Release: Northwind.NET v.2.0 (Feb 04, 2011)

ShamilS — Mon, 06 Feb 2012 15:42:33 GMT

Updated Release: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

ShamilS — Mon, 06 Feb 2012 15:42:04 GMT

Updated Release: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

ShamilS — Mon, 06 Feb 2012 15:32:08 GMT

Updated Release: Northwind.NET v.2.0 (Feb 04, 2011)

ShamilS — Mon, 06 Feb 2012 15:31:06 GMT

Created Issue: Memory Resources [6702]

Will_Tom — Tue, 03 Jan 2012 23:23:33 GMT

Well done on the new release (2.1) ... some interesting upgrades

One issue I noted is that the user controls seem to use an excessive amount of memory and do not release any memory when the user goes to the next control? I have been working on upgrading an app that implements user controls and have the same problem … any thoughts?

WIll

Updated Wiki: Documentation

ShamilS — Mon, 07 Feb 2011 01:42:33 GMT

Northwind.NET v.2.1 (.NET Framework 4.0) 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.10.0.0.0/ - 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

P.S.

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=1.0.0.0,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil/Northwind.NET.XBAP.FE.exe, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil, type=win32

System.Windows.Markup.XamlParseException:
'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=4.0.0.0, 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.

P.P.S. Setting WPF browser application to work in Intranet mode

1. Set Security as "Full Trust"

2. Edit App.config

<?xml version="1.0"?>
<configuration>
<connectionStrings>
<add name="NorthwindNETEntities" connectionString="metadata=res:///NorthwindEntityDataModel.csdl|res:///NorthwindEntityDataModel.ssdl|res://*/NorthwindEntityDataModel.msl;provider=System.Data.SqlClient;provider connection string="Data Source=NANT\SQLEXPRESS;Initial Catalog=NorthwindNET;Integrated Security=True;MultipleActiveResultSets=True"" providerName="System.Data.EntityClient" />
</connectionStrings>

<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>
</configuration>

3. Get application running from within VS2010

Updated Wiki: Documentation

ShamilS — Mon, 07 Feb 2011 00:13:27 GMT

Updated Wiki: Documentation

ShamilS — Fri, 04 Feb 2011 15:21:57 GMT

Released: Northwind.NET v.2.1 (.NET Framework 4.0) (Feb 04, 2011)

Fri, 04 Feb 2011 15:20:22 GMT

Updated Release: Northwind.NET v.2.1 (.NET Framework 4.0) (фев 04, 2011)

ShamilS — Fri, 04 Feb 2011 15:20:22 GMT

Updated Release: Northwind.NET v.2.1 (.NET Framework 4.0) (фев 04, 2011)

ShamilS — Fri, 04 Feb 2011 14:57:49 GMT

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.10.0.0.0/ - sample MS Reporviewer 10.0 ASP.NET web site

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

P.S.

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=1.0.0.0,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil/Northwind.NET.XBAP.FE.exe, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=d590cb1df9b1ff3f, processorArchitecture=msil, type=win32

System.Windows.Markup.XamlParseException:
'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=4.0.0.0, 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.

Updated Release: Northwind.NET v.2.0 (фев 04, 2011)

ShamilS — Fri, 04 Feb 2011 14:52:23 GMT