recompile after powercli upgrade

[MrBWare]

We have a process that need powercli.
vSphere was upgrade to 6.7 making us to upgrade to powercli 6.5 from 5.5.
after application upgrade, what else would i need to do, recompile?
Visual Studio is expensive, what can i use to recompile, if that's even the case?

[LucD]

Are you saying that you have an application that is compiled with the PowerCLI DLLs?

I'm afraid the only option is to recompile your application with the new DLLs.

And the price of VS has not a lot to do with PowerCLI, so I'm not sure what you are actually asking here?

[MrBWare]

More like PowerCLI need recompile.  I was told I would need VS to compile it.

Right now, with what we have when PowerCli get executed, got an error with something like it was still looking for version 5.5.

I'm not really sure how this process works.  I don't even know where to start.

This process was provided from another team who's has more development skills.  That person who was the owner of the source code now left the company leaving me hanging trying to decode this process.

I'm assuming this process with PowerCLi is to communicate with VMware.

I will try to replicate the error and capture the error and share.

[LucD]

If you could elaborate a bit on that application.
Is it a script (.ps1 file) or an .exe?

[MrBWare]

Sorry.  Yes the process is .exe file.

in a directory, there are 3-4 files associated together.

1. process.exe <-- ?compiled?

2. process.exe.config <-- manually input data

3. process.pdb

4. VMware.Vim.dll

[LucD]

I'm afraid that this is indeed a local application that uses a PowerCLI DLL.

Since that seems to be a local developed app, there is not a lot I can do I'm afraid.

[MrBWare]

That's too bad. So was I correct, process.exe is compiled.  Are there any .exe compiler?  I would like to see what task it is doing.

[LucD]

It's not obvious, but there might be some possibilities.

See for example this StackOverflow article.

[MrBWare]

So I was able to get help with recompile, using his VS.

I'm getting error:

Message: Unable to log in to virtual center: An error occurred while making the

HTTP request to https://vcentername.com/sdk​

This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in
the HTTPS case. This could also be caused by a mismatch of the security binding
between the client and the server.
 

What does this means?

[LucD]

Exactly what the error says.

If you are using a self-signed certificate on your VCSA, you normally use Set-PowerCLIConfiguartion to set InavlidCertificateAction to Ignore.

Depending on the VCSA version you are using I suspect it will not accept TLS v1.0 anymore.

In PowerShell you can force the protocols to accept with a line like this

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls,[Net.SecurityProtocolType]::Tls11,[Net.SecurityProtocolType]::Tls12