DEV Community: Dan Schnau

.NET 8 Preview 3: Simplified Output Path format for Builds

Dan Schnau — Thu, 20 Apr 2023 19:31:26 +0000

If you're like me, you're used to finding your .NET build artifacts in /bin and /obj directories inside your source projects. It's been this way my whole career.

In .NET 8 Preview 3, this can be changed to dump the /bin and /obj artifacts into an .artifacts directory instead of the source root.

.NET Manager Chet Husk Writes about it in the comments of 'What's new in .NET 8 Preview 3' discussion.

I'd like to test this little feature out. First, I needed to install .NET 8 Preview 3. It required a system restart.

First, a new console app in a directory testartifactsoutput.

~#@❯ dotnet new console ❮ 

Welcome to .NET 8.0!
---------------------
SDK Version: 8.0.100-preview.3.23178.7

Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience..... *SNIP*

Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

----------------
Installed an ASP.NET Core HTTPS development certificate.
To trust the certificate run 'dotnet dev-certs https --trust' (Windows and macOS only).
Learn about HTTPS: https://aka.ms/dotnet-https
----------------
Write your first app: https://aka.ms/dotnet-hello-world
Find out what's new: https://aka.ms/dotnet-whats-new
Explore documentation: https://aka.ms/dotnet-docs
Report issues and find source on GitHub: https://github.com/dotnet/core
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli
--------------------------------------------------------------------------------------
The template "Console App" was created successfully.

Processing post-creation actions...
Restoring C:\danschnauprojects\testartifactsoutput\testartifactsoutput.csproj:
  Determining projects to restore...
  Restored C:\danschnauprojects\testartifactsoutput\testartifactsoutput.csproj (in 76 ms).
Restore succeeded.

The default behavior is still to build to the /bin directory.

~#@❯ dotnet build ❮ 
MSBuild version 17.6.0-preview-23174-01+e7de13307 for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.
C:\Program Files\dotnet\sdk\8.0.100-preview.3.23178.7\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targ
ets(287,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [C:\danschnaupr
ojects\testartifactsoutput\testartifactsoutput.csproj]
  testartifactsoutput -> C:\danschnauprojects\testartifactsoutput\bin\Debug\net8.0\testartifactsoutput.dll

Then, we create a Directory.Build.Props file.

~#@❯ dotnet new buildprops ❮ 
The template "MSBuild Directory.Build.props file" was created successfully.

The buildprops file is pretty sparse.

<Project>
  <!-- See https://aka.ms/dotnet/msbuild/customize for more details on customizing your build -->
  <PropertyGroup>

  </PropertyGroup>
</Project>

We add the UseArtifactsOutput flag to the file:

<Project>
  <!-- See https://aka.ms/dotnet/msbuild/customize for more details on customizing your build -->
  <PropertyGroup>
    <UseArtifactsOutput>true</UseArtifactsOutput>
  </PropertyGroup>
</Project>

Now I cleaned up the build by deleting the /bin and obj directories.

~#@❯ ls ❮ 

    Directory: C:\danschnauprojects\testartifactsoutput

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 4/20/2023 3:25 PM 212 Directory.Build.props
-a---- 4/20/2023 3:20 PM 105 Program.cs
-a---- 4/20/2023 3:20 PM 252 testartifactsoutput.csproj

And now, a build:

~#@❯ dotnet build ❮ 
MSBuild version 17.6.0-preview-23174-01+e7de13307 for .NET
  Determining projects to restore...
  Restored C:\danschnauprojects\testartifactsoutput\testartifactsoutput.csproj (in 64 ms).
C:\Program Files\dotnet\sdk\8.0.100-preview.3.23178.7\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targ
ets(287,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [C:\danschnaupr
ojects\testartifactsoutput\testartifactsoutput.csproj]
  testartifactsoutput -> C:\danschnauprojects\testartifactsoutput\.artifacts\bin\testartifactsoutput\debug\testartifactsoutput.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:01.20

Ooh, I see the .artifacts directory in the output there.

The /bin and /obj directories are now in their own /.artifacts folder. Sweet.

~#@❯ ls ❮ 1s 452ms  

    Directory: C:\danschnauprojects\testartifactsoutput

Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 4/20/2023 3:26 PM .artifacts
-a---- 4/20/2023 3:25 PM 212 Directory.Build.props
-a---- 4/20/2023 3:20 PM 105 Program.cs
-a---- 4/20/2023 3:20 PM 252 testartifactsoutput.csproj

~#@❯ ls .\.artifacts\ ❮ 

    Directory: C:\danschnauprojects\testartifactsoutput\.artifacts

Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 4/20/2023 3:26 PM bin
d----- 4/20/2023 3:26 PM obj

Identity Protocol improvements in ASP.NET Core 8

Dan Schnau — Mon, 10 Apr 2023 22:56:48 +0000

Last week, Jeremy Likness discussed improvements to Authentication and Identity features in ASP.NET Core 8.

I wanted to try some of it out, so I first went to install dotnet 8.0.0-preview.2. I think the downloads page looks slick.

OpenID Connect, IdentityServer, and Duende

Earlier this week, I talked about the terms Authentication vs Authorization. Now I'll use this chance to tie the terms to more technical details.

ASP.NET Core, in the past, used a third-party implementation of OpenID Connect called IdentityServer to provide authentication and authorization services. IdentityServer is an implementation of the OpenId Conect protocol, which itself is a layer over the OAuth 2.0 protocol that provides Authentication, which is a protocol for Authorization.

The Authorization story here starts with the OAuth 2.0 Authorization Framework. Oauth 2.0 is a framework for dealing with limitations of client-server authentication. There are a lot of good reasons to not implement client-server authentication. From this developer's perspective, the most attractive reason is that with OAuth, I as a software engineer, don't need to spend the time and money on implementing password security. This is because the OAuth protocol specifies an authorization layer that separates the client and server, enabling third parties to provide Authorization services.

OAuth 2.0 provides an authorization implementation. OpenID Connect provides an authentication implementation. And both are just protocols. That is - protocols that are instructions for software to implement to work with other software that implements the same protocols.

Back to the beginning. Until version 8, ASP.NET Core used a third party implementation of OpenId Connect called IdentityServer. In version 8, this dependency is removed, and developers will be able to pick from IdentityServer or any other number of OpenId Connect and OAuth 2.0 implementations.

Ostensibly, these changes will make it easier to create and ship "simple" auth systems that do things like use social logins - and I look forward to trying them out as they become available.

Authentication vs Authorization

Dan Schnau — Mon, 10 Apr 2023 14:14:51 +0000

Authentication and Authorization (AuthN and AuthZ) are terms that refer to discrete, specific concepts that can easily be confused.

Authentication is the process of proving that someone is who they claim to be.

Authorization is the process of granting access to a resource.

For instance, to buy alcohol, I must be at least 21 years old, as per legal requirements. When I try to make the purchase, the sales clerk will likely request my driver's license. By examining the photo on the license and confirming it to be of me, the sales clerk is performing Authentication. I have presented evidence that I am Dan Schnau, and provided a government-issued document with a photograph and other relevant facts, verifying my identity.

However, at this moment, the sales clerk has not allowed me access to the resource- alcohol. After proving my identity, the sales clerk will perform Authorization. The clerk will verify my date of birth on the driver's license, which will enable them to grant access, knowing that I have already proved who I am (via photo ID) and that I am authorized based on my age.

In summary, Authentication verifies identities, and Authorization grants access to resources based on those identities. It is critical to implement both measures for safe systems.

I asked ChatGPT to write 500 words about the software industry.

Dan Schnau — Fri, 31 Mar 2023 19:21:05 +0000

As an AI language model, it is difficult for me to express opinions or personal bias since my responses are generated entirely based on statistical patterns from the dataset I was trained on. However, I can provide a general overview of the current state of the software industry.

The software industry is one of the fastest-growing industries in the world. It has transformed almost every aspect of daily life, from how we communicate with each other to how we conduct business. The industry has seen exponential growth in the past few decades, with the increasing availability of processing power, deep learning techniques, and cloud computing. Software development has become easier, faster, and more affordable than ever before.

One of the key drivers of the industry's growth has been the rise of mobile devices. With more than 3 billion smartphones in use globally, software developers have had to adapt to the rapidly changing behavior and needs of consumers. This has led to a surge in the development of mobile applications, which have become indispensable for both business and personal use.

Another key driver of the software industry's growth has been the shift to cloud computing. Cloud computing has enabled businesses of all sizes to access affordable computing power and storage without having to set up their own IT infrastructure. This has democratized technology, making it accessible to small and medium-sized enterprises that previously did not have the resources to invest in IT infrastructure.

The software industry has also seen a shift in the way software is developed. The traditional model of developing software has been replaced by more agile approaches such as DevOps, which emphasizes collaboration, agility, and rapid iterations. These approaches have enabled businesses to be more responsive to market demands and to deliver software products faster.

However, the increasing reliance on software has also led to concerns around security and privacy. The rise of cybercrime has highlighted the need for secure software development practices, and companies are increasingly investing in cybersecurity measures to protect their assets and customers' information.

The software industry has also seen a shift in the business model, with more companies embracing open-source software. Open-source software allows businesses to access the source code of software products, customize them to meet their needs, and contribute back to the community. This has led to a flourishing ecosystem of software developers who share their knowledge and collaborate on projects.

Finally, the software industry is undergoing a shift towards automation and artificial intelligence (AI). AI has the potential to transform the way we develop software, making it more efficient and effective. AI-powered tools can help identify bugs and optimize code, freeing up developers' time to focus on more complex tasks. However, there are concerns around the impact of automation on jobs, and the industry must find a way to balance the benefits of automation with the need to protect jobs and skills.

In conclusion, the software industry is in a state of constant evolution. As technology continues to advance and consumer behavior changes, software developers must adapt to stay ahead of the curve. The industry's growth and increasing importance in almost every aspect of daily life are indicative of the potential it holds for the future. However, the industry must also address the challenges it faces, such as cybersecurity and the impact of automation on jobs. Overall, the software industry is a vital and exciting industry, and its future is full of promise.

Rules for Overcoming Worry

Dan Schnau — Wed, 25 Jan 2023 16:52:32 +0000

A few years ago I visited a used book store in Seattle. It had several cats hanging around with the customers, which was pretty cool.

I found a copy of How To Stop Worrying and Start Living by Dale Carnegie, of "How to Win Friends and Influence People" fame.

I bought it, and it's been a great book to keep around when I get stressed out.

One of the exercises in the book suggests creating your own rules for overcoming worry. I wrote my answers down and have copied them here.

Rules for Overcoming Worry

Remember that every moment is new. Past performance is not indicative of future results.
Meditate. Breathe relaxation and loving-kindness into your muscles, from head to toe.
Remember what your mother told you when you were a stressed out child (and has been so right about): "Most of the things you worry about will never even happen".
Focus on the present day in front of you. The distant future is of no concern. As Apollo Creed told Rocky Balboa as he trained to fight Clubber Lang: "There is no tomorrow!"

I put a lot of energy into stayling relaxed these days. I know that being stressed out will not only not help but rather it will harm me.

Affiliate notice

This page contains Amazon affiliate links.

Good Software Engineers are Business Analysts Too

Dan Schnau — Fri, 20 Jan 2023 18:31:35 +0000

Good software engineers have to understand the business they're working in.

If they don't, they're at the mercy of business analysts and project managers to explain what to do.

Some of my most successful moments in my career have been when I've taken on a role of business analyst and gone directly to the source for information on what needs to be built for the business.

In other words:

You gotta write code, and be this person too.

ChatGPT Is at the Peak of the Hype Cycle

Dan Schnau — Thu, 19 Jan 2023 16:01:39 +0000

ChatGPT is at the peak of the hype cycle.

You'll Never Do Agile Right

Dan Schnau — Wed, 23 Nov 2022 19:39:27 +0000

In the article for Agile Software Development, there are six thousand, eight hundred words and over 100 references.

The Agile Mainfesto is 73 words. Gobs and gobs of software has been written to "do agile". Every software shop I've encountered in the last decade has told me they use an agile software development process. Being an "Agile coach" is an entire career.

But the whole manifesto is just not all that.

The entire body reads as follows:

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

That's it. Focus on relationships with people, and actually solving problems.

Moreover, the Manifesto ends with a sentence to weasel out of any actual firm stance. The other stuff is also valuable.

You'll never do Agile right, because there's no way to prove that you're doing it right. Don't make user stories and have retrospective meetings just because it says to do so in some book or by some coach.

Do what works for whatever your situation. Just make sure your values and priorities are in order. That's the whole manifesto.