I was running a docker build against a .NET Web API project, on a Windows OS machine connected to a VPN and I was getting the error error NU1301: Unable to load the service index for source https://api.nuget.org/v3/index.json.
This fixed it for me…
{
"dns": [
"8.8.8.8"
],
"experimental": false
}
When you deploy your ASP.NET core (.NET 8) to an Azure web app, you’ll have likely created the app to work with Kestrel (so you can deploy to pretty much any environment). But when you deploy as an Azure Web App, you’re essentially deploying to an IIS application.
So we need for IIS to simply proxy across to our Kestrel app. We achieve this by adding a Web.config to the root of our published app. and we’ll have configuration such as below
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<location path="." inheritInChildApplications="false">
<system.webServer>
<handlers>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
</handlers>
<aspNetCore processPath=".\MyAspNetCoreApp.exe" stdoutLogEnabled="false" stdoutLogFile="\\?\%home%\LogFiles\stdout" hostingModel="inprocess" />
</system.webServer>
</location>
</configuration>
It’s, sometimes, useful to nest files within our solution within Visual Studio 2022 – we see this automatically with appsettings.json or .designer.cs files etc.
We can however make Visual Studio nest any files, so for example, create a file named .filenesting.json within your project’s folder, here’s an example which nests some .generated.cs files which I am using as my custom auto-generated code
{
"help": "https://go.microsoft.com/fwlink/?linkid=866610",
"root": true,
"dependentFileProviders": {
"add": {
"extensionToExtension": {
"add": {
".generated.cs": [
".cs"
]
}
}
}
}
}
Note: you will need to unload and reload your project to get Visual Studio to use the filenesting.
In this example if you have a MyLib.cs file a MyLib.generated.cs file the generated one will shows as a child/nested folder of the non-generated file.
You can actually use Visual Studio itself to create these files by
By default using Visual Studio will create your files with the Users AppData folders.
If you’re wanting to play around with Elixir in a REPL you can use iex.
Note: To exit iex just CTRL+C twice.
Within the shell we can simply type in code on a line and press enter to evaluate it. So for example type
le = [1,10,20]
press enter and the shell will display the list now bound to the value l.
Now type
length(l)
and the shell should display 3, the length of the list.
To get help from the shell, execute
h()
Compiling a module into iex
Whilst you’re developing your modules you might which to test them via the shell, in which case from you can load it when you start iex using (in this case my module in called math.ex)
iex math.ex
or if you’ve already started iex, simple use
c "math.ex"
The line above compiles your code and loads into iex so it’s now available to call from the shell.
If you want to view the exports on a module (in this example on my Math module), use the command
exports(Math)
I was messing around with Windows based docker images, running IIS and an ASP.NET 4.7.x application and wanted to connect to it’s “shell” to explore what was installed etc.
For Linux container you’ll probably use bash. From a Windows container we can just use powershell
Just change “the-container-id” to the id of the container you wish to connect to
docker container exec -it the-container-id powershell
When creating an an HTML document, we would include the lang attribute to specify the language of the content within the document.
This allows browsers, screen readers etc. to correctly interpret and present content and allows screen readers to pronounce words in the style of the language selected. So for example we’d have
<!DOCTYPE html> <html lang="en"> <!-- content --> </html>
Note that we use the short form language, i.e. “en” or long form such as “en-GB” or “en-US”
Obviously this would need to be changed if your application support i18n, so we might use something like the following, if we’re using something like the i18n package for React
document.documentElement.lang = i18n.language; // OR document.documentElement.lang = i18n.resolvedLanguage;
If you do not set the lang or set it to an empty string this simply means the language is unknown.
Whilst this post talks about the html tag, you can actually set the lang on other elements, such as paragraphs p so on a per element basis.
Azure offer a free static web site option, the process for creating a static web site is the same as creating one for a Blazor standalone application…
As part of this process, if you tie to application to your GitHub repo. you’ll also find a GitHub action’s CI/CD pipeline added to your repository which will carry out continuous deployment upon commits/merges to your main branch.
It’s likely you’ll want to map your Azure website name to DNS, I have my domain created with a different company so need to change DNS records
In my third party host I enter DNS record
In Azure in the static web app, select Settings | Custom domains and Add Custom domain on other DNS (if host is not in Azure)
Don’t forget to change the Azure supplied workflow
Whilst this is a pretty seamless experience, just usually waiting on CNAME and DNS to be updated etc. One thing to not forget is that the generated workflow file will need some changes to point to your app source etc.
At the end of the build_and_deploy_job you’ll see app_location, api_location and output_location, these need setting up for your application source location, if you are using Azure functions, then the API location and finally the output location. The first of these is the one you do need to add the others are optional.
I came across a situation where I needed to change some logic in my ASP.NET core application dependant upon whether I was running inside Kubernetes or an Azure Web app, luckily there is an environment variable that we can use (and whilst we’re at it, there’s one for Docker as well)
var isHostedInKubernetes =
Environment.GetEnvironmentVariable("KUBERNETES_SERVICE_HOST") != null;
var isHostedInDocker =
Environment.GetEnvironmentVariable("DOTNET_RUNNING_IN_CONTAINER") == "true";
One of the many cool things with Blazor is that we can actually use a Blazor component within a React application…
yarn create react-app my-app-js
In this example, we’ll use JS instead of Typescript, but I’ll show how to use Typescript later
dotnet new blazorwasm-empty -o BlazorComponents
<h3>Welcome to My Component</h3>
<button @onclick="UpdateCounter">OK</button>
<div>@_counter</div>
@code {
int _counter = 0;
private void UpdateCounter()
{
_counter++;
}
}
builder.RootComponents.RegisterAsCustomElement<MyComponent>("my-component");
The my-component is the name that gets used within the React app.
dotnet publish
<script src="_framework/blazor.webassembly.js"></script>
<div className="App"> <my-component></my-component> </div>
Now if we created our React application using Typescript, which is my usual way of doing this, using
yarn create react-app my-app-ts --template typescript
and if you follow all the instruction for the React side of things from above, you’ll find that there’s an error message displayed because <my-component> as it’s not an instrinsic JSX type, so the simplest way to handle this is to disable the error using ts-ignore, i.e.
<div className="App">
{/* @ts-ignore */}
<my-component></my-component>
</div>
Just noting this process here, but the full instructions can be found at Getting Started.
To create a React application using Vite, simply run
npm create vite@latest my-app -- --template react-ts
Obviously change my-app to your app. name and in this case I’m using the React Typescript template.
Then cd into the app. folder and run the following
npm install npm run dev