Create a simple non-docker version of App about azure-search-openai-demo-csharp

[Rickcau]

100% agree with this. I tried setting this up locally and I get all sorts of errors when running the azd up. One of the issues was with the docker part then once I got that fixed I am getting lots of other errors.

[Porkechebure]

The current source code is shit. And I mean horrid.
Like, they have a few bools to check for chat ready state, if response had arrived and such. A toy for kids. We put loads of bools for checking state when we were programming our first hello world stuff.
I don't use excuses and bland words, I say exactly what it is.
Many years into the field and since MS embraced OSS, all turned into shit.

They started to getting onto the bandwagon of all these shit js frameworks paradigms and now every application looks like a half baked inbreed between js frameworks and little of what the colossal and mature .NET framework was remained in it.

Now we are set to the js style:
Quintillions of config files and external tooling everywhere in every folder, totally untied from the code and you either have to get the ".NET fatigue" as it was for "Js fatigue" to read pages and pages of poorly written docs on the learn portal to be able to connect the wires togheter.

Same as of js, the whole introduction of a ton of tooling make it become like developing a react/angular app.
An ill, complex, fragile and immature ecosystem filled with immature tools written by anyone who think that can code.
You can resort to a bit of "standard" tooling that microsoft tries to set, but they make low effort to maintain them up to date because they (as every OSS) rely on community doing the work.

So now it's a total spaghetti code mess with nonsensical and unnecessary layers, injection forced everywhere with no real benefit just because "HEYYYY INJECTION IS COOOL WE ARE TOP EDGE DEVS IF WE USE IT"

No wonder you get any sort of errors running azd commands.
Heck, I also use projects that use azure, cosmos, openai services, blob storages, azure functions and everything else on azure, but I maintain a simple structure that had evolved little from what I was doing in the past, mostly to introduce only the REAL BENEFICIAL TOOLS, and not a ton of useless shit.
For example Docker that ease up lot of the environment setup or Linq which helps a ton (i know, it's old, it's just to mention) or minimal APIs that speed up the process of having an API.

My projects resemble much those of 10 years ago and everything works damn fine. A pity we can't use WCF anymore and we are forced with that BS rest, which is an excuse to mount up a lot of word salad over sending some json/xml strings over the http protocol and to make it the js way: untyped havoc with lot of errors, or for example all the HTTP verbs which are now "super duper standard if you don't use it you're a bad dev". They made a total hot dumster fire with them with all that FromBody, FromQuery and so on that barely connects well with all the http verb attributes (HttpPost, HttpGet etc) and causes troubles to everyone because params don't arrive in controllers.
And don't say it's me. Search on google and it's literally INFESTED with people looking up for help on those subjects.

[Coruscate5]

FWIW - you can deploy each resource to Azure individually, then starmap your resources back to IaC through bicep. We also had issues with the Docker architecture for Linux with private Nuget repos, so you can always just deploy your Website architecture to Windows App Service.

[Porkechebure]

FWIW - you can deploy each resource to Azure individually, then starmap your resources back to IaC through bicep. We also had issues with the Docker architecture for Linux with private Nuget repos, so you can always just deploy your Website architecture to Windows App Service.

Lmao, they boast bicep, dev containers and all that sort of stuff to make the whole experience "seamless" than you have to do those shenaningans you are describing to deploy a simple app.

Really nice.

Oh and for the record, if you try to run "azd up" on a valid Ai Studio subscription it doesn't even work.

It gives

---

RESPONSE 400: 400 Bad Request
ERROR CODE: InvalidTemplate

{
"error": {
"code": "InvalidTemplate",
"message": "Deployment template validation failed: 'The provided value for the template parameter >'openAiResourceGroupLocation' is not valid. The value 'centralus' is not part of the allowed value(s): >'canadaeast,eastus,eastus2,francecentral,switzerlandnorth,uksouth,japaneast,northcentralus,australiaeast'.'.",
"additionalInfo": [

A pity I didn't touch nothing and the Central US zone is what they put into it.
Lol.

You might say: "Hey just change it manually".
Beside being a despicable reply by someone who boasts simplicity (microsoft, not you), the funny just begins now:

I put as value in .env "northcentralus" like this:
AZURE_LOCATION="northcentralus"

and now it says

"message": "Deployment template validation failed: 'The provided value for the template parameter 'location' is not valid. >The value 'northcentralus' is not part of the allowed value(s): >'centralus,eastus2,eastasia,westeurope,westus2,australiaeast,eastus,francecentral,japaneast,nortcentralus,swedencentral,swit>zerlandnorth,uksouth'.'.",

Basically, it just flips the array of choices over taking out the one you put in config.

Same if you try a third one:

"error": {
"code": "InvalidTemplate",
"message": "Deployment template validation failed: 'The provided value for the template parameter 'openAiResourceGroupLocation' is not valid. The value 'swedencentral' is not part of the allowed value(s): 'canadaeast,eastus,eastus2,francecentral,switzerlandnorth,uksouth,japaneast,northcentralus,australiaeast'.'.",
"additionalInfo": [
{
"type": "TemplateViolation",
"info": {
"lineNumber": 1,
"linePosition": 1384,
"path": "properties.template.parameters.openAiResourceGroupLocation.allowedValues"
}

How awesome is this?
It's just insanely magic.

I'm even in difficulty to choose wheter cry or laugh out of disappointment

[thomas-christiansen]

Totally agree. WHY do they have to over complicate things. Make a simple console app that illustrates the connection between the services, then developers can decide for them self to use docker, kubernetes, a space shuttle or what the h. they want.