aspdotnet — Attach to Process

Increase WCF Service Call Timeout in ASP.NET Web API Project

Mon, 12 Jul 2021 17:30:22 +0000

A few months ago, I ran into a situation where I had to increase the timeout for a WCF service call, that my ASP.NET Web API was making. It wasn't as straightforward as just adding configuration to a config file, like you would do with a WCF service. You actually have to do it in code. The answers to the stackoverflow question listed below, helped a lot in figuring out a solution for it.

Link: How to increase the timeout values for a WCF service in a dot net core 2.1 project – Stack Overflow

In your Web API code, you can create a partial class for the WCF client you are trying to call. In that class, you should be able to get to the Endpoint object. This object allows you get to the WCF bindings where you can set the timeout values. Then you can do something similar to the code I have below to set the timeouts.

TimeSpan timeSpan = new TimeSpan(hours: 0, minutes: 0, seconds: timeoutInSeconds);
Endpoint.Binding.CloseTimeout = timeSpan;
Endpoint.Binding.OpenTimeout = timeSpan;
Endpoint.Binding.ReceiveTimeout = timeSpan;
Endpoint.Binding.SendTimeout = timeSpan;

Tags: #AspDotNet #AspDotNetWebApi #WCF

Discuss... or leave a comment below.

WriteFreely Archive Page Generator

Tue, 05 Jan 2021 02:00:00 +0000

Finished work on the WriteFreely Archive Page Generator Blazor app. While it does say WriteFreely, you can still pass in Write.as as the instance name and your Write.as alias, and it will work just the same.

Tags: #AspDotNet #Blazor #WriteAs

Discuss... or leave a comment below.

Blazor WASM Caching Issue

Tue, 05 Jan 2021 02:00:00 +0000

While working on a Blazor WASM project last week, I noticed that no matter what changes I make to the index.html and app.css files, they were not reflected whenever I open up the site on IIS Express. It turns out to be a caching issue. All I needed to do, was hit CTRL + F5 after the site loads, and it will pull in my changes.

Tags: #AspDotNet #Blazor

Discuss... or leave a comment below.

Write.as Popular Posts – Blazor WASM App

Tue, 22 Dec 2020 02:00:00 +0000

Update 4/23/2021: The write.as team has introduced some rate-limiting features on their API to combat spam bots. That stopped this Glitch app and my other Blazor WASM apps from working.

Was supposed to create an “Unpopular Posts” Blazor WASM app, but ended up creating the opposite. Anyway, I managed to make the app flexible by having it use query string parameters. That means that you can use the app and embed it into your own Write.as page/site. Just follow the instructions in the readme.

Link: Write.as Popular Posts – Blazor WASM App

Tags: #AspDotNet #Blazor

Discuss... or leave a comment below.

Blazor Web Apps

Mon, 08 Jun 2020 22:45:20 +0000

Was playing around with Blazor and created this site. It is a static site that has web apps written in C# instead of Javascript. Why? Because with Blazor, you can.

Next step is figuring out how I can embed Blazor apps.

Tags: #AspDotNet #Blazor #DotNetCore

Discuss... or leave a comment below.

Hundreds of practical ASP.NET Core samples to learn the fundamentals | Scott Hanselman

Wed, 19 Feb 2020 00:00:00 +0000

This is a great resource for anyone who wants to get started with C# and .NET Core.

Link: Hundreds of practical ASP.NET Core samples to learn the fundamentals

Tags: #Bookmarks #AspDotNet #DotNet #DotNetCore

Discuss... or leave a comment below.

ASP.NET Core and .NET Core and the Web Development Stack Timeline - Iris Classon

Wed, 22 May 2019 23:00:00 +0000

Iris Classon wrote a good lengthy post about the history of .NET web development and how it all lead to the development of the .NET Core that we have today. As someone who doesn't get to work as much on the web dev side of things, this was a very informative read for me. I think it is a good read for any .NET developer, so check out her post by following the link below.

ASP.NET Core and .NET Core and the Web Development Stack Timeline

Tags: #Bookmarks #AspDotNet #DotNet #DotNetCore

Discuss... or leave a comment below.