15,867,568 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Mr Ellipse (Top 2 by date)
Mr Ellipse
15-Aug-15 3:29am
View
There are quite a few things to be done here.
If you create a virtual directory in IIS, and point it to the UNC/network share, you can then use Server.MapPath() to access files. The account IIS is running under will need appropriate permissions on the UNC share.
Apart from that small piece of setup, all the class libraries you should need reside in System.IO namespace!
You can use FileInfo and DirectoryInfo classes to CRUD directories or files. System.IO.Compression.GZipStream can be used to compress or decompress files.
Hope this points you in the right direction!
Mr Ellipse
30-Jul-15 3:00am
View
You got it!
EF tracks the entire 'object graph' of changes. Because you are adding a new BatchProduct to the Data Context, when SaveChanges() is called, it will evaluate the BatchProduct.Product and BatchProduct.Batch navigation properties, and perform an insert/update on those as well.
The EF Data Context does all the work via proxy wrappers, which tracks changes made to it in memory as soon as an object is added to, or retrieved from the Data Context.
Batch = batch is not a typo. Its just a concise way of setting the .Batch property of new BatchProduct(). ;)
Cheers,