I've installed the EF B3 on several machines without a problem. Could you
elaborate on what problems you're having? (you could also ask on the
ADO.NET Preview forums
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=533&SiteID=1)
Thanks,
Shawn Wildermuth
http://adoguy.com
http://wildermut
Hi all,
I'm having trouble installing the latest EF beta. I found this
http://benhblog.com/2007/12/installing-latest-version-of-adonet.html, but I
can't get the "undocumented VS patch" (sic) to work. Did somebody manage to
do this? I'm in middle of planning next version of our system and I really
r
On Feb 5, 2008 5:04 PM, Michael Sharpe <[EMAIL PROTECTED]> wrote:
> There are several assumptions in your statement that are not accurate:
>
> 1. different clients are *already* writing to a single networked file
> system
> This is not true. We have a final process called our Merge that takes the
I don't know this for a fact, but it's my guess that something in the area of
hard links, junctions and reparse points might be able to provide this
functionality on an NTFS file system.
Phil Wilson
-Original Message-
From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]
There are several assumptions in your statement that are not accurate:
1. different clients are *already* writing to a single networked file
system
This is not true. We have a final process called our Merge that takes the
individual pieces and recombines them into a new file. Not very
efficient
I'm curious what other OS/file systems have this capability
natively...it's an interesting, though edge-case, optimization. A quick
Google only turns up Lustre
http://ieeexplore.ieee.org/iel5/4215348/4215349/04215390.pdf?isnumber=42
15349&prod=CNF&arnumber=4215390&arSt=267&ared=274&arAuthor=Yu%2C+W
> Sadly, no. We have no control over the consumer application of the
> required data file. It cannot accept the data in chunks or pieces.
> It
> cannot accept a data stream either so providing it data on the fly is
> out
> of the question. It can only accept it as a single data file.
> Otherwis
There's no documented function in Windows to do this, as the
concept "append file x to file y". Thus, nothing in .NET to do this.
You'd have to write something that modified the filesystem. In FAT it
would be pretty easy, simply modify the file allocation table for the
first file (replacing the
Michael,
I don't think a .Net group is the best place for this question.
You'd better try some Windows groups.
Guys like Mark Russinovich http://technet.microsoft.com/en-us/sysinternals
would know the answer immediately, if you get the chance to him ;-)
Regards, Robert
-Ursprüngliche Nach
Sadly, no. We have no control over the consumer application of the
required data file. It cannot accept the data in chunks or pieces. It
cannot accept a data stream either so providing it data on the fly is out
of the question. It can only accept it as a single data file. Otherwise
we wou
I appreciate the performance concern and will certainly take that into
consideration. The problem that I currently face is that we have a
computational grid system. This system is responsible for performance
analytics and returning results. Part of this process also is to generate
export fil
> Is it at all possible to combine 2 (or more) data files together without
> A) opening the data files to read and B) creating a "new" file out of
> them?
Can you change the problem to make it easier to solve?
Depending upon what you need to do with the end-product, can you change
the reading appl
Interesting problem... My knowledge of the low level APIs is quite limited,
but I'd start by looking around for examples of how defragmenters work - it
seems reasonable that if they can shift around the data directly on the
drive, they should allow you to mess with the file system record itself
(a
Take a look at the FileStream class. It gives you the possibility to
Append to a file. I see how in the short term appending to a file
(while causing fragmentation) is a speedy process but think about it
in the long run; when you try to read the data from these files back
they will be heavily fra
I suspect that will be filesystem specific. FAT, FAT32 or NTFS.
i think you're going to need to be closer to the hardware than the .net
sandbox allows.
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] Behalf Of Michael Sharpe
Sent: Tuesday, February
The overload on the constructor assumes that data is going to be written
into the file which is being opened for Append. I do not want this. I
basically want to trick the file system into merging the two data files
into 1 file without having to physically migrate any data. I want a
second fi
Look at the overloads for the ctor to the "FileStream" class.
you can specify a "Mode", which can be "Append".
-Original Message-
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] Behalf Of Michael Sharpe
Sent: Tuesday, February 05, 2008 11:20 AM
To: ADVANCED-DOTNET@DI
Is it at all possible to combine 2 (or more) data files together without
A) opening the data files to read and B) creating a "new" file out of
them?
For example, lets say I have one file that is 20MB and a second file that
is 50MB. What I want to have happen is for the second data file to just
be
Thanks for the great referrals folks.
The profiling API looks very powerful, but a little beyond the skills here.
The quick win i think is going to be PostSharp.
It also makes the most sense in terms of ease of future maintenance by other
developers. Gotta work with the lowest common denominator
19 matches
Mail list logo
