tugberkugurlu / prowebapi.samples Goto Github PK

/cc: @AlexZeitler

Which framework version should we target? .NET 4.0 or .NET 4.5?

/cc: @AlexZeitler

What should we have as a development workflow for the individual chapter source code (not for the sample application)? Here is what I think:

• The master branch of this repository is the stable branch.
• We should work on so-called feature branches. E.g: Ch11-AuthFilterProject. Every feature branch should be branched off of master branch.
• When the code under a feature branch is ready, we can follow the below approach:
  • You can send a PR from your forked repo by targeting tugberkugurlu:master branch. Then, I will merge it into master branch (We both have push and pull rights to tugberkugurlu/ProWebAPI.Samples project but it is better if one person is responsible for merging).
  • Since I don't have a chance to fork this repo, I will directly merge from my feature branch into master.
  • Before sending a PR, we should always pull from tugberkugurlu:master to keep our feature branch up to date.
  • After the merge, we can delete the feature branch or keep it. That doesn't matter much.

At the end, we won't struggle much and just give the zipped version of master branch.

/TO: @AlexZeitler

Do you approve this type of HttpClient usage inside a controller?

https://github.com/tugberkugurlu/ProWebAPI.Samples/blob/master/Chapter19/MultipleAsyncInOne/MultipleAsyncInOne/APIs/CarsController.cs

As long as the base address uses https://, is all the data (to and from the server) encrypted with HttpClient (assuming the remote http service's certificate is valid)? Do we need to act specifically to enable that?

Any idea?

/cc: @AlexZeitler

Let's put together the list of External libraries we will be using here than we will put the final version as a page.

Here are some of them:

• Moq - http://code.google.com/p/moq/
• jQuery - http://jquery.com/
• Knockout - http://knockoutjs.com/

https://github.com/tugberkugurlu/ProWebAPI.Samples/blob/master/Chapter19/HttpClientSamples/SampleAPIApplication/Models/CarsContext.cs#L70

should be:

    public bool TryUpdate(int id, Car car) {

        var index = cars.FindIndex(x => x.Id == id);

        if (index >= 0) {

            cars[index] = car;
            return true;
        }

        return false;
    }

At the end, make sure that all projects are on .NET 4.5 and uses the RTM Web API packages.

/TO: @AlexZeitler

Do you think that would be non-sense to have a WPF sample for async HttpClient methods in async chapter? https://github.com/tugberkugurlu/ProWebAPI.Samples/tree/Ch19-HttpClient/Chapter19/HttpClientSamples

I have created one and it seems to be the best fit since I cannot use async/await in a console app.

/cc: @AlexZeitler

As we need to provide the source code which we use inside the book, we should structure it in a way that it can be easily found.

• We can create separate folders for each chapter and under that folder, separate solutions for each project which is used inside that chapter. On the other hand, as ASP.NET Web API ships through NuGet, we might end up with lots of duplicate package files since we have separate solutions.
• We might have one solution for whole book, and separate the chapters with solution folders. The disadvantage of this way is that one needs to open the whole solution (which will take time as the project grows) even if s/he wants to work with only one project inside it.

Here you can download the source code for the Pro ASP.NET MVC book unde Source Code/Downloads section. They used separate solutions approach but at the time which that book was written, ASP.NET MVC was inside the GAC and not lots of NuGet package files.