Develop Reference

Oracle.ManagedDataAccess.Client is already defined - Updates may only occur at the configuration level where it is defined

I have written an app that uses Oracle.ManagedDataAccess and sent the app (the bin/Debug folder to be precise) to another company. Now, when they start the app they get the following error:
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Section or group name 'oracle.manageddataaccess.client' is already defined. Updates to this may only occur at the configuration level where it is defined.
There seems to be something very basic about those NuGet packages or the Oracle package in particular that I do not understand. The Oracle.ManagedDataAccess.dll is in the folder I sent to the other company. My understanding was that once an appropriate .NET version is installed on their computers, my app must run regardless of what else is installed on the machine. But the error message sounds to me like some other app also works with Oracle.ManagedDataAccess and is somehow considered the master for it and doesn't allow my app to run? This must be a misunderstanding on my part, but what what else could that message mean?
Sorry for sounding stupid. I know, it is most likely that I made some mistake myself, for how could Windows allow another app to rule mine? Could someone please explain what the error message means and what I can do to make my app run on any company's computers?

Cannot post activity. Unauthorized

For some reason, I am unable to start even the simplest bot in Bot Framework Emulator.
Steps to reproduce:
In VS2019, create new Echo Bot (Bot Framework v4 - .NET Core 3.1) project (using Bot Framework v4 SDK Templates for Visual Studio)
Run project without making any changes whatsoever (empty strings for MicrosoftAppIdand and MicrosoftAppPasswordin in appsettings.json)
Start Bot Framework Emulator
http://localhost:3978/ opens up in the browser without issue but in the Emulator I get the below errors:
Cannot post activity. Unauthorized.
POST 401 directline/conversations/<conversationId>/activities
What could be causing these errors with such a minimal project? My understanding is this should just work straight out of the box when running on localhost and no security credentials have been provided.
I am using a work computer and I'm wondering if there is something 'behind the scenes' blocking a connection somewhere/somehow? I have no idea where to look, though. It works fine on another computer and was working fine on this machine when I last tried a couple of months ago so I'm really confused.
Any clues or suggestions on how to debug this problem would be greatly appreciated.

Azure Bot Service code update with continues developmemt

We had set up a bot service with LUIS in c# for a few months, now on we want to enable continues development with VSTS. we had set up the project in VSTS and commit the source without problem. And the bot service is configured with VSTS and able to deploy successfully without errors. But we found the bot still operating with sample code logic and the code still a sample code in the build tab. Is it any solution to let the bot service replace the old sample code?

I personally recommend using the SDK over Azure Bot Service, but that is a personal preference. I say this because it feels much like any project in Visual Studio and there are fewer steps to set up continuous deployment and other things like debugging locally.
For Azure Bot Service continuous deployment please read through this link to get started and make sure you did not miss a step. There are also instructions to debug your bot locally here. I hope this helps, please let me know if it does not.

WPF Application designed in VS 2012 won't run on Windows 7 machine

I've designed a WPF C# application using Visual Studio 2012. The application, which is simple enough, runs fine on my Windows 8 machine using the ClickOnce deployment method. The datagrid displays the content from a SQL Server database and performs all of it's other functions just as I've designed it to, but when I attempt to install it on a Windows 7 machine it immediately crashes and I'm not sure why. The Windows 7 computer I'm trying to install the application on has .NET 4.5 running on it, but is there anything else that computer needs to have installed on it in order to run applications developed with VS 2012. This is my first attempt to install an application developed with VS 2012 on a Windows 7 machine, so I'm not sure if there's another step that I'm missing here. Any help you guys can provide would be greatly appreciated. Thank you.

The message you stated "The application has stopped working and that if Microsoft has a solution..." is an indicator of one of the following:
The Framework is disabled; though 4.5 is installed several root instances are built on the foundation which are apart of Framework 2.0. This particular Framework can cause issues for 3.0, 3.5, 4.0, and even 4.5.
The System.EnterpriseServices.dll is damaged in the Framework. Which needs to be connected back to the Global Assembly Cache (GAC).
And another common issue is the machine.config file log in the Framework Folder can be corrupt and needs to be replaced with a valid one.
There are others that can occur within the System Policy Folder as well, which may require you to use the .Net Cleanup Tool and reinstall the Framework. But before you do any troubleshooting you should go to the Event Viewer and get details of what is going on.
Try these steps first for me:
Windows Key + R
When the run prompt appears type: appwiz.cpl
Go to the left hand side: Turn Windows Features On or Off
Turn Framework 3.5 on if it isn't already; if it is already on go to Step 5.
Turn off the Framework; then reboot.
Once rebooted follow steps 1-4 again.
Now at this point I would suggest trying the application again. If it fails try this:
Open Start
Type 'cmd' in Search
Right Click and Run as an Administrator
Type %windir%\Microsoft.Net\Framework\v2.0.50727\ngen.exe update
Then type: sfc /scannow
The Native Regeneration tool will try to repair the Framework back to a factory state; the System-File-Checker will attempt to fix any errors indicated in Windows. If it can't it will say 'it found integrity violations'.
Those are the steps I would do for general support; but you really should try and locate an error message. As the Framework can become a huge ordeal to cleanup and fix. If you provide more information I will revise my response to help address it.
Hopefully that helps.

.net (winforms, not asp) multi-server deployment

I have a small .NET WinForms application, and couple of linux servers, DEV and CL1,CL2..CLN (DEV is development server and CL* are servers which belons to our clients, they are in private networks and it's a kind of production servers)
I want an update mechanism so that
(1) i develop a new version and publish it to a DEV
(2) users of DEV-server install latest version from DEV
(3) users of CL2 (employees of client2) install stable version from CL-2 directly
(4) application checks for updates using server it was installed from (so, if it was installed from CL-2, it should check CL-2 for updates)
(5) i should be able to propogate the update to a selected CL-server (using just file copy & maybe sed; not republishing), if i want that (and if i don't, that CL-server will have an old version until manually i update it)
I tried to use clickonce, but looks like it meets only first two requirements.
What should i do?

ClickOnce should handle 1-4 to be honest. All that would be needed is that for each site you want to deploy/update from, you'll need it to have its own publish, which after looking at your specifications is not incorrect to do.
What you could then do in order to make 5. applicable, is create an automated process to re-publish the file. This could perform a publish and then upload to the correct server.
Remember that ClickOnce needs a new manifest per version, and a new version requires a publish, so I'm not sure that you'll get around 5. with a simple file replacement.

Kyle is right. But for the 5th note, you just need to copy the deployment, and then use mage to modify the installation URL and point it to the new server, and then re-sign the manifests.

I support an app that we deploy to a DEV, QA, PROD servers. The way I handled this is that
I created created a cmd file that has command line calls to MSBUILD. It builds the app once for each server with the appropriate URLs and switches. I give my DEV and QA builds a different AssemblyName that way I can run all 3 environments side by side. This way my build process is automated and I don't have to publish at all.
Here's an article that describes the parameters you can use.
http://msdn2.microsoft.com/en-us/library/ms165431(VS.80).aspx
#Kyle,
For the above solution can the different versions run side by side or do you get errors indicating the app is already installed.