Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing References and other issues. #27

Open
Delgathar opened this issue Dec 25, 2021 · 1 comment
Open

Missing References and other issues. #27

Delgathar opened this issue Dec 25, 2021 · 1 comment

Comments

@Delgathar
Copy link

Delgathar commented Dec 25, 2021

Hello,

Attached are a couple explanatory images.

In the Kindle edition, many of the images are clipped. There seems to be nothing I can do to see the entire image. There is no zoom function and right-clicking only gives me a dictionary option. I've also tried switching from dual pane to single pane or changing the margins, but it only makes the entire page bigger or smaller, including the image, but it doesn't un-crop the cropped image. I'm using Windows Kindle viewer, so it might work fine on a tablet, but not on the pc. Not all images have this problem, just the images with explanatory writing on the right side of the images.

The second image points at a reference that is supposed to show in my IDE. It doesn't. Unfortunately, Google isn't much help. There are thousands of false hits connecting reference and Visual Studio. Usually, when you point out something in the IDE you give a tip to reset it if it doesn't show in the students. Could you please let me know what I need to do? I remember it used to show now that you pointed it out, but I can't remember when it vanished.

25eb0f6f-7113-45bf-84a7-610bd5ac832f
61a22297-1b34-404d-b191-43a506e26689

There are no page numbers on Kindle Edition. This makes it hard to apply errata or point out where a problem page might be.

private void Timer_Tick(Object source, ElapsedEventArgs e) { InvokeAsync(() => { tenthsOfSecondsElapsed++; timeDisplay = (tenthsOfS

I don't understand how this goes up in tenths of a second when the ++ operator is used. It says elsewhere that ++ increments by 1. Not .1. I'd expect tenthsOfSecondsELapsed = tenthsOfSecondsElapsed + .1;

The debugger kept tripping Avast antivirus. I ended up having to uninstall it because even with exceptions added, it kept triggering and blocking the debug exercise.

When creating WPF Apps, the instructions say to make WPF .net. But there is not just a WPF .net. There is WPF .net Core, and WPF .net Framework. does it matter which I choose? VS doesn't make clear what the difference is . Core and Framework are a bit too synonomous.

I loved the Debug exercise in Chapter 1. The code that popped the error was already "cleared" and apparently had nothing to do with the new code. Usually, when I see a debug exercise it is something along the lines of. "Ok, now take this working program and we'll delete the period. Now run it." Which is all very good, but the problem is obvious. This was a real head-scratcher, so when the exercise asked how many times did I hit continue before it finally broke, I was also surprised, because it never occurred to me before that I should count such a thing.

Overall, great so far. Pressing into chapter 2 now.

Thank you.

@andrewstellman
Copy link
Collaborator

Thanks so much for letting us know that you're seeing these issues! I really appreciate you taking the time to give such detailed feedback—it really helps us. I'll get in touch with the folks at O'Reilly and see we if we can get it sorted out. In the meantime, you can see the full images in the the PDF of chapters 1 to 4: Head_First_CSharp_4e_chapters_1_to_4.pdf (if you DM me on Twitter I'd be happy to have the folks at O'Reilly send you a PDF of the whole book).

You're right—the timer ticks every tenth of a second, so it adds 10 to tenthsOfSecondsElapsed each tick. That's okay because later on in the code we divide tenthsOfSecondsElapsed by 10 before we actually display it:

timeTextBlock.Text = (tenthsOfSecondsElapsed / 10F).ToString("0.0s");

And yes, you're right—they changed the WPF options in Visual Studio a bit since the book was printed. You should choose WPF .NET Core (but if you chose WPF .NET Framework the whole exercise should still work exactly the same, so it hopefully shouldn't prevent any learning).

Also, I really appreciate the feedback about the Debug exercise! We really try to lean on the Visual Studio debugger as a learning and exploration tool throughout the book. I hope you like the rest of it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants