User profile for mltgames

I fixed the issue manually I added this inside SmartAssembly.exe.config <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false" /> and <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2" /> Basically it will allow the use of TLS 1.2 Here is my SmartAssembly.exe.config <?xml version="1.0"?> <configuration> <configSections> <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net, Version=1.2.11.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a"/> </configSections> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2" /> </startup> <runtime> <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false" /> </runtime> <log4net>    </log4net> </configuration> Thanks again for your help, / comments

I fixed the issue manually I added this inside SmartAssembly.exe.config <AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false" />and <supportedRunti...

0 votes

I added 1433 to my connection string and it work. Here is my config if it can help someone. <SmartAssembly.Settings> <Options> <Database ConnectionString="Data Source=192.168.0.8\SmartAssembly,1433; Initial Catalog=smartassembly; User Id=sa; Password=password" DatabaseEngine="1" LastProject="{ae726256-376b-4c6a-80f4-505fef2a73cf}" MasterConnectionString="Data Source=192.168.0.8\SmartAssembly,1433; Initial Catalog=master; User Id=sa; Password=password" Server="192.168.0.8\SmartAssembly,1433" /> </Options> </SmartAssembly.Settings> / comments

I added 1433 to my connection string and it work. Here is my config if it can help someone. <SmartAssembly.Settings> <Options> <Database ConnectionString="Data Source=192.168.0.8\SmartAssembly,1433...

0 votes

Humm where is the UBR version for windows 10? its good to have the build # but the UBR (Update Build Revision) is a nice to have. / comments

Humm where is the UBR version for windows 10? its good to have the build # but the UBR (Update Build Revision) is a nice to have.

0 votes

Thanks for the quick reply, It's just a suggestion / a nice to have. Currently, it displaying 10.0.15063.0 for me instead of 10.0.15063.296. 296 is my UBR. Like the latest version on wikipedia https://en.wikipedia.org/wiki/Windows_10 it is 10.0.15063.296, with the 296 you know which monthly updates are installed on the machine. / comments

Thanks for the quick reply, It's just a suggestion / a nice to have. Currently, it displaying 10.0.15063.0 for me instead of 10.0.15063.296. 296 is my UBR. Like the latest version on wikipedia http...

0 votes

Thanks for your quick reply, I made the change into my registry and it's working. All files can be embbed except the file Microsoft.Threading.Tasks.dll. If I embbed this file I have this crash on load: FileLoadException: Could not load file or assembly 'System.Core, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes' or one of its dependencies. The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047) I removed this file from the embbeding and I made a copy of "Microsoft.Threading.Tasks.dll" version 1.0.168.0 into my project exe folder and it's now working. Maybe smart assembly do something different with this file but this is not really an issue for us. Thanks again. / comments

Thanks for your quick reply, I made the change into my registry and it's working. All files can be embbed except the file Microsoft.Threading.Tasks.dll. If I embbed this file I have this crash on l...

0 votes

I finally found the issue. The server name was invalid. It was set to 127.0.0.1:443 instead of the hostname:443 Inside the IIS server configuration. / comments

I finally found the issue. The server name was invalid. It was set to 127.0.0.1:443 instead of the hostname:443 Inside the IIS server configuration.

0 votes

Thanks for your quick reply, I just sent the report. / comments

Thanks for your quick reply, I just sent the report.

0 votes

Thanks for your response, it worked! [image] / comments

Thanks for your response, it worked!

0 votes

I have the exact same issue while I'm building 10x the same build. It look like there is a memory leak somewhere in 6.8.0.121 / comments

I have the exact same issue while I'm building 10x the same build. It look like there is a memory leak somewhere in 6.8.0.121