vs_BuildTools.exe --add Microsoft.VisualStudio.
Workload.WebBuildTools --passive<Project DefaultTargets="Build" ToolsVersion="17.0"><VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">17.0</VisualStudioVersion><Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v17.0\WebApplications\Microsoft.WebApplication.targets" Condition="false" />
"C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\MSBuild.exe" /property:Configuration=Release "YourSolution.sln" -restore -p:RestorePackagesConfig=true > Build.log
You have a .NET solution that uses NuGet package manager.
You have many files in the packages folder and want them to be downloaded to your build server.
cd D:\Build\Source nuget restore YourSolutionFileName.sln
"C:\Program Files\Microsoft Visual Studio\2022\Professional\Msbuild\Current\Bin\MSBuild.exe" "../YourSolution.sln" -restore -p:RestorePackagesConfig=true
Update-Package
Update-Package –reinstall
Could not load file or assembly 'Microsoft.IdentityModel.Tokens.Saml, Version=8.0.2.0
<bindingRedirect oldVersion="0.0.0.0-8.1.2.0" newVersion="8.1.2.0" />
Your software installer (e.g. an EXE or MSI file) is warned by Microsoft Defender. You want to remove the warning so that your users can trust your software.
You need to sign your software installer using an EV code signing certificate.
SSL certificate is a cryptographic certificate (technically named X.509) issued by a Certificate Authority as a file for encrypting and decrypting data between a client and server.
SSL certificate is usually valid for one domain in 1 year.
Code singing certificate is a cryptographic certificate (technically named X.509) issued by a Certificate Authority as a file for placing a digital signature on a file, program, or software.
Code signing certificate is usually valid for signing file, program or software from 1 year to 3 years.
Code signing certificate does not relate to domain.
EV code signing certificate is a code singing certificate (technically named X.509) that is issued on USB or HSM or Cloud Signing Service (not a file) by a Certificate Authority for placing a digital signature on a file, program, or software to bypass MS Defender warning.
EV code signing certificate is usually valid for signing file, program or software from 1 year to 3 years.
EV code signing certificate does not relate to domain.
When signing file, program or software using an EV code signing beside presence of USB or HSM or Cloud Signing Service an additional one-time password (OTP) is usually required for security.
The core part of a certificate is a secret string called private key.
All the certificates have this same core part. The difference is just where this string will be stored.
– This secret string can be stored in a machine/server (standard certificate) and can be exported and imported to other machines/servers, e.g. via PFX files with private keys.
– This secret string can be stored in a USB (this is a requirement for EV certificate). In this case, it can be imported to the USB but then could NOT be exported from the USB and imported to other locations.
– This secret string can be stored in a HSM (hardware security module, usually a physical card with cryptoprocessor chip or a certified virtual machine, USB can be considered a HSM too) (this is a requirement for EV certificate). In this case, it can be imported to the HSM but then could NOT be exported from the HSM and imported to other locations.
– This secret string can be stored in a Cloud Code Signing Service (this is actually a specific certified HSM virtual machine) (this is a requirement for EV certificate). In this case, it can be imported to the Cloud Code Signing Service but then could NOT be exported from the Cloud Code Signing Service and imported to other locations.
If we have 3 physical servers and we use the USB storage approach for EV Code Signing certificate then we need 3 USB sticks (duplicates) that contain the same certificate.
If we use HSM or Cloud Code Signing Service then we just need one HSM or one Cloud Code Signing Service account.
– Purchase an EV code signing certificate.
– Retrieve the USB containing private key and temporary token password.
– Install software to connect to the USB, e.g. SafeNet Authentication Client, and change the temporary token password.
– Find and copy the SignTool.exe utility from Visual Studio Tools to a location.
– Enable Single Logon feature of SafeNet Authentication Client on Client Settings > Advanced so that we can pass the EV certificate password to SignTool.
– On SafeNet Authentication Client, right click the EV certificate and export the public certificate (.CER file).
– On SafeNet Authentication Client, click the EV certificate and retrieve the key container name of the EV certificate.
– Sign the software installer using the command below.
SignTool sign /f myCert.cer /csp "eToken Base Cryptographic Provider" /k "[{{TokenPasswordHere}}]=KeyContainerNameHere" myFile.msi /tr http://timestamp.digicert.com /td sha256 /fd sha256
– Verify the signing using the command below.
SignTool verify /pa myFile.msi
You have a .NET solution with many projects.
You need to deliver the solution to a client very frequently.
You need to clean up all intermediate folders and files to reduce the package size and make the result look tidy.
You want to automate this process to reduce cleaning up time.
rd /s /q $(ProjectDir)obj
cd $(TargetDir)
del *.config
del *.pdb
del *.xmlrd /s /q $(ProjectDir)obj: Remove the obj folder in the project directory.
cd $(TargetDir): Move to the output directory.
del *.config: Delete all the config files in the output directory.
del *.pdb: Delete all the pdb files in the output directory.
del *.xml: Delete all the xml files in the output directory.
You can modify these commands or add new commands for your specific purpose.
In order to delete all the obj folders recursively you can
@echo off
@echo Deleting all OBJ folders...
for /d /r . %%d in (obj) do @if exist "%%d" rd /s/q "%%d"
@echo OBJ folders successfully deleted :) Press any key to close the window.
pause > nul3. Execute the DeleteObjFolders.bat file.
You need to quickly capture and analyze requirements for building a prototype or proof of concept for an enterprise system.
You need to read existing source code to add a new feature or fix a bug or clone its features to another language or system.
Example:
const maskPhone = (val) => {
const x = val.replace(/\D+/g, '').match(/(\d{0,3})(\d{0,3})(\d{0,4})/);
return !x[2] ? x[1] : `(${x[1]}) ${x[2]}` + (x[3] ? `-${x[3]}` : ``);
};
export { maskPhone }If you are not sure about what the JavaScript code above does then try to learn
Another example:
<div class="container">
<iframe class="responsive-iframe" src="https://www.youtube.com/embed/u9Dg-g7t2l4"></iframe>
</div>.container {
position: relative;
overflow: hidden;
width: 100%;
padding-top: 56.25%; /* 16:9 Aspect Ratio (divide 9 by 16 = 0.5625) */
}
/* Style the iframe to fit in the container div with full height and width */
.responsive-iframe {
position: absolute;
top: 0;
left: 0;
bottom: 0;
right: 0;
width: 100%;
height: 100%;
}
If you are not sure about what the HTML and CSS code above do then try to learn
position: relative , position: absolute , overflow: hidden do.
You want to use Git to version your files or share your files with other people.
git init git config user.email "[email protected]" git config user.email git config user.name "Huy Bien" git config user.name git config credential.helper "" cd C:\Users\admin\Downloads\code git remote add origin -f https://github.com/huybien/asp.net-core.git git pull origin main / * or * / git pull origin master
cd C:\Users\admin\Downloads\code git init --initial-branch=main git config user.email "[email protected]" git config user.email git config user.name "Huy Bien" git config user.name git config credential.helper "" git remote add origin https://github.com/huybien/asp.net-core.git git fetch --all git add *.* git commit -m "new files added" git push -u origin main
git init git config user.email "[email protected]" git config user.email git config user.name "Huy Bien" git config user.name git config credential.helper "" git add *.* git commit -m "first commit" git branch -M main git remote add origin https://github.com/huybien/asp.net-core.git git push -u origin main
git config user.email "[email protected]" git config user.email git add *.* git commit -m "CP form" git branch -M main git push -u origin main
git pull origin main /* or */ git branch --set-upstream-to=origin/main main git pull
git fetch --all git reset --hard origin/main git clean -fd git pull
git -C C:\Users\admin\Downloads\code fetch --all git -C C:\Users\admin\Downloads\code reset --hard origin/main git -C C:\Users\admin\Downloads\code clean -fd git -C C:\Users\admin\Downloads\code pull
cd C:\Users\admin\Downloads\code git log --oneline git reset --hard 4355842 // where 4355842 is a version id.
git rm -r --cached .
git config --get remote.origin.url
You need to fix a bug. However it takes you a lot of effort to fix. The fix may also not be reliable. How can you avoid this situation?
Why do I need to learn about software construction?
Knowing how to write code does not mean that you know how to create real-world software.
In real world projects, you will need to know how to manage your code, how to read the existing code, how to write code following standard styles, how to ensure that your code is working, how to automate your the process of building, testing and deploying your code, how to handle errors in your application, how to optimize your code for better speed, how to write secure code, how to avoid code duplication, how to create readable code, how to create code faster.
That’s why you need to learn about software construction.
What can I do after finishing learning software construction?
You will know how to create real world software with a team.
Hmm! Is it really useful?
If you doubt its usefulness then you can delay learning it until you are tasked to create a software system and you complete a half of it and are stuck there because when you add one more feature you will get tons of bugs due to the new code, or when you finish fixing 1 bug, you get 3 other bugs due to the code modification.
An other scenario is when it takes another person 2 weeks to read 1000 lines of the code that you wrote in order to fix a bug or to add a new feature because your code is unstructured.
Another scenario is when you are asked to improve some existing code for better performance or to refactor some code for clarity before adding a new feature but you do not know how to accomplish the task.
Alright! What should I do now?
Software construction requires a lot of reading. In order to get familiar with software construction you will need to read at least below books. Please read this Steve McConnell (2004). Code Complete. Microsoft Press book first.
After that please read this Jon Loeliger and Matthew McCullough (2012). Version Control with Git: Powerful Tools and Techniques for Collaborative Software Development. O’Reilly Media book.
Alternatively, you can read this Ben Collins-Sussman et al. (2011). Version Control with Subversion book.
After that please read this Paul M. Duvall et al. (2007). Continuous Integration Improving Software Quality and Reducing Risk. Addison-Wesley book.
After that please read this Robert C. Martin (2009). Clean Code: A Handbook of Agile Software Craftsmanship. Pearson Education book.
After that please read
– this Andy Hunt, Dave Thomas and Matt Hargett (2007). Pragmatic Unit Testing in C# with NUnit. Pragmatic Bookshelf book, and
– this Kent Beck (2002). Test Driven Development: By Example. Addison Wesley book.
After that please read
– this Martin Fowler et al. (1999). Refactoring Improving The Design Of Existing Code. Addison Wesley book, and
– its newer version Martin Fowler (2019). Refactoring. Improving the Design of Existing Code. 2nd Edition. Addison-Wesley Professional also.
If you have to work with legacy code then please read
– this Michael Feathers (2004). Working Effectively with Legacy Code. Prentice Hall PTR book, and
– this Diomidis Spinellis et al. (2003). Code Reading: The Open Source Perspective. Addison-Wesley Professional book.
After that if you are familiar with .NET then please read
– this Matthew MacDonald and Bill Hamilton (2003). ADO.NET in a Nutshell. O’Reilly Media book to learn how to use a data provider to access data sources, and
– this Brian L. Gorman (2020). Practical Entity Framework. Apress book to learn how to use an ORM to access data sources, and
– this Suhas Chatekar (2015). Learning NHibernate 4. Packt Publishing book to learn how to use an ORM with mapping technique to access data sources, and
– this Brian Larson (2017). Microsoft SQL Server 2016 Reporting Services. McGraw-Hill Education book to learn how to use a reporting system, and
– this Justin Richer and Antonio Sanso (2017). OAuth 2 in Action. Manning Publications book to learn how to use authentication and authorization frameworks and libraries, and
– this Matt Perdeck (2010). ASP.NET Site Performance Secrets. Packt Publishing book to learn how to reduce a web application response time.
After that please read
– this Elton Stoneman (2020). Learn Docker in a Month of Lunches. Manning Publications book, and
– this Elton Stoneman (2021). Learn Kubernetes in a Month of Lunches. Manning Publications book. You should learn basic concepts, then try exploring the tool using official documentation if you get any issue with example code in the book.
After that please read this Yevgeniy Brikman (2022). Terraform – Up and Running. O’Reilly Media book.
Terminology Review:
After finishing learning about software construction please click Topic 12 – Software Testing to continue.