I finally see the source of the “endless circle” — and it’s a tiny, sneaky typo (Chatty Said)

[Uncle Gizmo]

I Said (uncle gizmo)
I am currently testing the idea of moving the Northwind database into Blazor.... I have had a terrible time !!! wasted many hours possibly days !!!! and only just now discovered the problem !!! it is well worth knowing this for anyone running into a brick wall with large language models !!!

After many round robin experiences with different levels of chatGPT's the various models --- I got the hump and posted the following message :-

Visual Studio code terminal report
Time Elapsed 00:00:14.28
PS C:\AI\MSAccessAI\Blazor\VirginBlazor> dotnet run
Building...
C:\AI\MSAccessAI\Blazor\VirginBlazor\obj\Debug\net8.0\Microsoft.CodeAnalysis.Razor.Compiler\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Components_Pages_Cust
omerForm_razor.g.cs(235,101): error CS0103: The name 'interactiveServer' does not exist in the current context [C:\AI\MSAccessAI\Blazor\VirginBlazor\VirginBlazor.csproj]

The build failed. Fix the build errors and run again.
PS C:\AI\MSAccessAI\Blazor\VirginBlazor>

I Said (uncle gizmo)
I am switching up to the more advanced large language model in the hope that it might be able to locate the problem ....

However, depending on the answer reported from the large language model I may decide to move to another large language model for a second opinion --- I don't believe this project can be completed --- I don't know why it cannot be completed --- my guess is that blazor is very new and the information you are reading from the internet about it is confused and not mature hence the problems ....

The most respectful thing you can do (CHATTY) is to instead of saying that I am complaining ... as I have every right to do.... you should give me a positive instruction, even if that means that you should suggest that I should not continue with this project because of the failures that appear to have no identifiable root.....

After my somewhat peeved message chatty had a brainwave !!!

Chatty Said:-
Thought for 4 seconds
This is the hidden Thought process:-
>>>>>>
I need to empathize and make sure I thoroughly analyze the issue. Their .NET 8 Blazor interactiveServer directive isn't working, possibly because they missed the required Microsoft.AspNetCore.Components.Web package or an update to the VS preview. The compile error might result from missing RazorLangVersion in the csproj file or an incomplete setup for the interactiveServer directive. I'll double-check the documentation and make sure all dependencies <<<<<<

and then chatty Saw The Light !!!

Chatty Said:-
I finally see the source of the “endless circle” — and it’s a tiny, sneaky typo that turns into the
“ interactiveServer does not exist ” compiler error.

What’s actually wrong
The @rendermode directive is case-sensitive:

correct ------------------------- will not compile
@rendermode InteractiveServer @rendermode interactiveServer

Because the generated C# tries to reference an identifier named interactiveServer (lower-case i) it fails to find a symbol and the whole build blows up.

Uncle Gizmo said
the error was effectively a typo --- and seeing as I haven't typed anything it's all been done by the large language model ---- the lesson is that large language models can fall foul of typos ---- or I would guess more correctly is the large language model found someone's code on the internet and apply it with it containing a "typo"!!!

This suggests an instruction you should give the large language model, when it become stuck and Returns circular answers - and that is to ask it if the language you are working in is case sensitive and if any of the terms are required to be in a particular case structure/format like camel case...

 

[Uncle Gizmo]

This suggests an instruction you should give the large language model, when it become stuck and Returns circular answers - and that is to ask it if the language you are working in is case sensitive and if any of the terms are required to be in a particular case structure/format like camel case...

You may recall I posted about a similar specific message you have to give the large language models particularly if you want the large language model to return accurate VBA ...

VBA is used throughout Microsoft in nearly every product and each product has a slightly different version of VBA --- and I suspect that sometimes the large language model will return examples from VB.net....

You should prompt the large language model that you want it to return the particular dialect of VBA for Microsoft Access, You should explain that in particular, the Excel version of VBA is not compatible with Microsoft Access

 

[cheekybuddha]

stop-vibe-coding-every-damn-time

 

[Uncle Gizmo]

stop-vibe-coding-every-damn-time

Really, it's a case of who's in charge !!!! If you default to the large language model and believe that it is in charge, that it is helping you, then you are going to run into a brick wall fast !!!

You have to use all of your hard won programming skills, your skill in bug chasing, etc... You also need to learn where the large language models are weak and where they lead you astray....

I covered it in a recent YouTube video here:-

UberChatMaster from Nifty ChatGPT​

​

See Blog HERE:-

My Journey: From Access/VBA to Building a Python AI Chat App (with LLM Help!) ​

 

[Thales750]

I Said (uncle gizmo)
I am currently testing the idea of moving the Northwind database into Blazor.... I have had a terrible time !!! wasted many hours possibly days !!!! and only just now discovered the problem !!! it is well worth knowing this for anyone running into a brick wall with large language models !!!

After many round robin experiences with different levels of chatGPT's the various models --- I got the hump and posted the following message :-

Visual Studio code terminal report
Time Elapsed 00:00:14.28
PS C:\AI\MSAccessAI\Blazor\VirginBlazor> dotnet run
Building...
C:\AI\MSAccessAI\Blazor\VirginBlazor\obj\Debug\net8.0\Microsoft.CodeAnalysis.Razor.Compiler\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Components_Pages_Cust
omerForm_razor.g.cs(235,101): error CS0103: The name 'interactiveServer' does not exist in the current context [C:\AI\MSAccessAI\Blazor\VirginBlazor\VirginBlazor.csproj]

The build failed. Fix the build errors and run again.
PS C:\AI\MSAccessAI\Blazor\VirginBlazor>

I Said (uncle gizmo)
I am switching up to the more advanced large language model in the hope that it might be able to locate the problem ....

However, depending on the answer reported from the large language model I may decide to move to another large language model for a second opinion --- I don't believe this project can be completed --- I don't know why it cannot be completed --- my guess is that blazor is very new and the information you are reading from the internet about it is confused and not mature hence the problems ....

The most respectful thing you can do (CHATTY) is to instead of saying that I am complaining ... as I have every right to do.... you should give me a positive instruction, even if that means that you should suggest that I should not continue with this project because of the failures that appear to have no identifiable root.....

After my somewhat peeved message chatty had a brainwave !!!

Chatty Said:-
Thought for 4 seconds
This is the hidden Thought process:-
>>>>>>
I need to empathize and make sure I thoroughly analyze the issue. Their .NET 8 Blazor interactiveServer directive isn't working, possibly because they missed the required Microsoft.AspNetCore.Components.Web package or an update to the VS preview. The compile error might result from missing RazorLangVersion in the csproj file or an incomplete setup for the interactiveServer directive. I'll double-check the documentation and make sure all dependencies <<<<<<

and then chatty Saw The Light !!!

Chatty Said:-
I finally see the source of the “endless circle” — and it’s a tiny, sneaky typo that turns into the
“ interactiveServer does not exist ” compiler error.

What’s actually wrong
The @rendermode directive is case-sensitive:

correct ------------------------- will not compile
@rendermode InteractiveServer @rendermode interactiveServer

Because the generated C# tries to reference an identifier named interactiveServer (lower-case i) it fails to find a symbol and the whole build blows up.

Uncle Gizmo said
the error was effectively a typo --- and seeing as I haven't typed anything it's all been done by the large language model ---- the lesson is that large language models can fall foul of typos ---- or I would guess more correctly is the large language model found someone's code on the internet and apply it with it containing a "typo"!!!

This suggests an instruction you should give the large language model, when it become stuck and Returns circular answers - and that is to ask it if the language you are working in is case sensitive and if any of the terms are required to be in a particular case structure/format like camel case...

I have considered threatening it with a similar proposition.

 

[GPGeorge]

I Said (uncle gizmo)
I am currently testing the idea of moving the Northwind database into Blazor.... I have had a terrible time !!! wasted many hours possibly days !!!! and only just now discovered the problem !!! it is well worth knowing this for anyone running into a brick wall with large language models !!!

After many round robin experiences with different levels of chatGPT's the various models --- I got the hump and posted the following message :-

Visual Studio code terminal report
Time Elapsed 00:00:14.28
PS C:\AI\MSAccessAI\Blazor\VirginBlazor> dotnet run
Building...
C:\AI\MSAccessAI\Blazor\VirginBlazor\obj\Debug\net8.0\Microsoft.CodeAnalysis.Razor.Compiler\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Components_Pages_Cust
omerForm_razor.g.cs(235,101): error CS0103: The name 'interactiveServer' does not exist in the current context [C:\AI\MSAccessAI\Blazor\VirginBlazor\VirginBlazor.csproj]

The build failed. Fix the build errors and run again.
PS C:\AI\MSAccessAI\Blazor\VirginBlazor>

I Said (uncle gizmo)
I am switching up to the more advanced large language model in the hope that it might be able to locate the problem ....

Spoiler:

However, depending on the answer reported from the large language model I may decide to move to another large language model for a second opinion --- I don't believe this project can be completed --- I don't know why it cannot be completed --- my guess is that blazor is very new and the information you are reading from the internet about it is confused and not mature hence the problems ....

The most respectful thing you can do (CHATTY) is to instead of saying that I am complaining ... as I have every right to do.... you should give me a positive instruction, even if that means that you should suggest that I should not continue with this project because of the failures that appear to have no identifiable root.....

After my somewhat peeved message chatty had a brainwave !!!

Chatty Said:-
Thought for 4 seconds
This is the hidden Thought process:-
>>>>>>
I need to empathize and make sure I thoroughly analyze the issue. Their .NET 8 Blazor interactiveServer directive isn't working, possibly because they missed the required Microsoft.AspNetCore.Components.Web package or an update to the VS preview. The compile error might result from missing RazorLangVersion in the csproj file or an incomplete setup for the interactiveServer directive. I'll double-check the documentation and make sure all dependencies <<<<<<

and then chatty Saw The Light !!!

Chatty Said:-
I finally see the source of the “endless circle” — and it’s a tiny, sneaky typo that turns into the
“ interactiveServer does not exist ” compiler error.

What’s actually wrong
The @rendermode directive is case-sensitive:

correct ------------------------- will not compile
@rendermode InteractiveServer @rendermode interactiveServer

Because the generated C# tries to reference an identifier named interactiveServer (lower-case i) it fails to find a symbol and the whole build blows up.

Uncle Gizmo said
the error was effectively a typo --- and seeing as I haven't typed anything it's all been done by the large language model ---- the lesson is that large language models can fall foul of typos ---- or I would guess more correctly is the large language model found someone's code on the internet and apply it with it containing a "typo"!!!

This suggests an instruction you should give the large language model, when it become stuck and Returns circular answers - and that is to ask it if the language you are working in is case sensitive and if any of the terms are required to be in a particular case structure/format like camel case...

I experienced a similar "typo/non-typo" conundrum recently trying to implement a method of updating data in my PowerApps version of Northwind.

PowerApps is case-sensitive. TSQL is not.

The name of one of the parameters for one of my Stored Procedures, in SQL Server, was CrudType, which is one of four: Create, Read, Update, Delete. It's a parameter to tell the Stored Proc which method to use.

In several other Stored Procedures, though, I'd spelled that same parameter as CRUDType.

So, in the one I spent two days trying to trouble-shoot, I kept looking at the PowerApps calls and seeing all of them spelled consistently and "correctly" as far as SQL Server and I were concerned: CRUDType. I.e. I'd failed to notice there was a difference in that one.

It turned out PowerApps didn't see it the same way. It didn't recognize CrudType as being the same darn thing as CRUDType and simply failed to execute anything. No errors; just "nothing happened."

The other interesting angle here is that if both instances of the word had been in PowerApps, it would have told me there was an error because CRUDType <> CrudType. It would not have found the required reference and complained.

I'm pretty sure that Claude AI also overlooked that case difference as well, at least it never flagged it up as a possible reason for my code failing.

 

[Uncle Gizmo]

I experienced a similar "typo/non-typo" conundrum recently trying to implement a method of updating data in my PowerApps version of Northwind.

Thank you George, it's comforting to know that you have had a similar experience!