EdmBuilder.cs is missing

[Vaccano]

EdmBuilder.cs is missing

[wardbell]

Wow. There is some kind of nuget restore madness at work here and I have NO IDEA why it doesn't work. I created a repro and posted my complaint on StackOverflow. I'll fix it when they tell me how.

Meanwhile, the workaround is to manually uninstall and reinstall the "breeze.edmbuilder" package. In the package console enter the following:

uninstall-package breeze.edmbuilder
install-package breeze.edmbuilder

If they don't give me the fix soon, I'll bury a copy of the missing file in the sample itself.

Sorry about this.

[wardbell]

SInce I last wrote, I've learned a few things.

First, I learned that nuget restore is not the same as nuget install ... see the exchanges and updates to my post on StackOverflow*.

Second, I now see that you did NOT download the sample from the breeze site but rather from the source in github. Yes, I know you told me that ... but I didn't read your question carefully enough to see that.

You cannot expect simply to build the samples from the github source!

We do not check in the packages file and we intentionally exclude the breeze libraries from the sample source in github.

Our samples-zip building process knows how to get these missing libraries and include them. But you cannot achieve the same effect simply by asking Visual Studio to build the samples for you.

You may be able to create working samples by doing the following in Visual Studio:

1. Restore the packages
2. In the package manager console enter: Update-Packages -Reinstall

I think this will actually work for the OData sample.

However, this is not guaranteed to work for all samples and will almost certainly be inadequate for some of them. Certain samples depend upon files in _breeze.labs_ that are not distributed through nuget packages and/or not listed in the sample's packages.config file. You would have to go get these files manually from their homes in one of the breeze github repositories.

I'm sorry about this. As I said, our samples-zip building process knows how and where to get the "missing" files. But we were not prepared for you to build the samples yourself from the github source.

Clearly you can do so if you're willing to hunt down the missing pieces.

Meanwhile, we'll put our heads together and try to come up with something better.

Thanks for your patience and understanding.

[Vaccano]

Ward,

Thank you for looking into my issue.

I was able to get it to work by reinstalling the breeze.edmbuilder package.

At the time I send the email, I could not find the download from the breeze site. I was looking for the http://www.breezejs.com/samples/doccode. The Doc Code page refers you to the todo example.

At the time I did not get that we were not meant to get the doc code example. So I kept digging. I found on the sample page the first entry about the samples in general. That lead me to follow the link to github. The link to github does not mention that the samples do not build correctly when downloaded from there (that might be a nice addition to that pagehttp://www.breezejs.com/samples/about-samples)

Either way, I got everything working now. Thank you for your help! Breeze is fantastic!

Stephen Schaff

From: Ward Bell [mailto:[email protected]]
Sent: Saturday, April 26, 2014 12:35 AM
To: Breeze/breeze.js.samples
Cc: Vaccano
Subject: Re: [breeze.js.samples] EdmBuilder.cs is missing (#16)

SInce I last wrote, I've learned a few things.

First, I learned that nuget restore is not the same as nuget install ... see the exchanges and updates to my post on StackOverflow*http://stackoverflow.com/questions/23304274/nuget-restore-fails-on-build-but-works-manually.

Second, I now see that you did NOT download the sample from the breeze site but rather from the source in github. Yes, I know you told me that ... but I didn't read your question carefully enough to see that.

You cannot expect simply to build the samples from the github source!

We do not check in the packages file and we intentionally exclude the breeze libraries from the sample source in github.

Our samples-zip building process knows how to get these missing libraries and include them. But you cannot achieve the same effect simply by asking Visual Studio to build the samples for you.

You may be able to create working samples by doing the following in Visual Studio:

1. Restore the packages
2. In the package manager console enter: Update-Packages -Reinstall

I think this will actually work for the OData sample.

However, this is not guaranteed to work for all samples and will almost certainly be inadequate for some of them. Certain samples depend upon files in breeze.labs that are not distributed through nuget packages and/or not listed in the sample's packages.config file. You would have to go get these files manually from their homes in one of the breeze github repositories.

I'm sorry about this. As I said, our samples-zip building process knows how and where to get the "missing" files. But we were not prepared for you to build the samples yourself from the github source.

Clearly you can do so if you're willing to hunt down the missing pieces.

Meanwhile, we'll put our heads together and try to come up with something better.

Thanks for your patience and understanding.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-41461490.

---

The information transmitted by this e-mail and any included
attachments are from ARUP Laboratories and are intended only for the
recipient. The information contained in this message is confidential
and may constitute inside or non-public information under
international, federal, or state securities laws, or protected health
information and is intended only for the use of the recipient.
Unauthorized forwarding, printing, copying, distributing, or use of
such information is strictly prohibited and may be unlawful. If you
are not the intended recipient, please promptly delete this e-mail
and notify the sender of the delivery error or you may call ARUP
Laboratories Compliance Hot Line in Salt Lake City, Utah USA at (+1
[phone] ext. 2100