I had created a project to access the properties of SheetSet and as well as AutoCAD Vault functionalites including Checkin to Server, CheckOut from server and all. It was developed using C# based on AutoCAD 2012 .dll files. And tested using AutoDesk Vault 2012 server. It worked fine, But the same code, i.e the same .exe file is not working with AutoDesk Vault 2015 server. Even the log In into the server is not happening.But normal accessing of SheetSet properties is working good, without any problem.
Now, It keepon saying as credentials problems., I'm pretty sure it's not the actual problem.
My Question is:
1. "Is the code differs based on the AutoCAD version..?".
2. "If it is, Is there any possibility to write code once, and access for all kinds of versions..?".
Please do the needful, any help would be appreciateable., Thanks.
Vault 2012 clients are not compatible with Vault 2015 server (http://justonesandzeros.typepad.com/blog/2014/03/whats-new-in-the-vault-2015-sdk.html).
You have to change references, update some portions of code, update the .NET framework version (4.5 for Vault 2015) and recompile.
Finally I found my answer.
From AutoDesk 2013 product, they are following new kind of pattern.
So older version before 2012 are not compatible. But newer versions from 2013 to 2015, it supports compatibility (using a set of 5 or 6 dll files).
Related
I have been trying to get a successful build for my game in Unity 2018.2.1f1 and Visual Studio 2017 15.8.0.
After trying unsuccessfully to get a successful build / package / WACK for the windows store with all/every different configuration, I tried a totally blank default Unity, UWP platform app, generated a visual studio project. generated some icons, associated it with an app I had in the store. Built it, packaged it and run the WACK tests.
FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API ExecuteAssembly in uwphost.dll is not supported for this application type. WinTest2.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. WinTest2.exe has an export that forwards to this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information:
What do I have to do to make a successful app build that I can actually get into the store. (What configuration, what unity / visual studio versions.) I have tried later versions of unity 2018.2.1 and 2018.2.2 (i think) and could not get a successful build out of them.
A while ago, i could not get a successful build out of Unity, so I reinstalled Win 10 Pro, Unity and Visual Studio. Still problems persist.
Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."
I have a project that was created in VS2008, and updated to VS2013 recently. I am trying to use the Microsoft.JET.OLEDB.4.0 provider to connect to a MS Excel file and it is throwing the error:
The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local
machine."** (It throws the same error when I use the
Microsoft.ACE.OLEDB.12.0 provider, except replace the JET with the ACE
reference).
However, when I create a brand new project in VS2013 and attempt to use the exact same code that uses these two providers, it works perfectly fine.
I'm running Windows 7 64-bit, with Office 32-bit and Visual Studio 2013 Ultimate 64-bit. Any idea what the difference would be between a new project created in VS2013 and a project that's been converted to 2013 from 2008?
Everything I can find says to set the Application Configuration Platform to x86, but when I do, it causes my project to error when building. I can certainly provide any code snippets that may be useful in assisting.
The Microsoft.Jet.OLEDB.4.0 provider is not supported in 64-bit environments.
The following is one of several links I found explaining essentially the same information.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/cfb9efe8-4de2-40b6-b817-553c91b9f9c6/the-microsoftjetoledb40-provider-is-not-registered-on-the-local-machine?forum=csharpgeneral
you need to download and install the 64bit version of the Microsoft Access Database Engine 2010.
You can download it from here: http://www.microsoft.com/en-us/download/details.aspx?id=13255
I know that I in the past was able to find the code used for the visual studio part of the azure sdk.
Need to see how visual studio selects certificate and generate remote access passwords when creating cloud services. But I have had no luck searching around in https://github.com/WindowsAzure for it
Need the c# code that selects a certificate and uploads it to azure for the deployment.
Not sure where the actual SDK source is, but I've posted this solution on SO and my blog for Securing Azure ServiceConfiguration values for Enterprise Deployment. Writing the code to encrypt/decrypt is trivial and full examples are provided. Adding the certificate to a deployment is also easy - just add it to to role settings. Depending on which SDK you are using, you may have to run with elevated privledges.
I wrote an application with .Net4 and C# and also deploy it to user system with install shield.
After I changed few lines of code, one of my Winforms automatically disposes** without error in client system which has .Net4 but does not have Visual Studio installed.
All prerequisites are installed and it used to work fine...
If I install Visual Studio in client's system, it will work perfectly.
I tried to debug it but visual studio does not find any exception.
Please help
Form may contain components that are not present in client's system.
It depends upon way in which you are deploying your application.
General way is:
Install framework.
Copy-Paste debug folder to client's system.
Bring shortcut to desktop.
OR
Simply publish the application.
Copy paste publish folder to cliet's System.
Execute publishing setup.
Bring shortcut to desktop.
It works in this way.
Hope its helpful
You wrote on the user machine .Net 4 Client framework is installed. Try to uninstall it and install full .Net 4 framework (here is a link to MS download site).
Those 2 lines that you have added may now reference the features that are available only in full .Net 4 installation. (Unfortunately you did not post those lines so we can only guess what the problem is).
With Visual Studio full .Net 4 is installed and maybe because of this your app starts to work after VS installation.
See Difference between .NET 4 Client Profile and Full Framework download for more details.
Would anyone mind explaining (or pointing me to a tutorial) how to setup an SQL embedded server with Visual Studio Express edition?
I'm not concerned with getting the Designer tab working, but I'm trying to achieve a few basic things:
Access the database via file path
read/write to database file
password to connect to database (not too big of an issue)
The solution I've been pointed to was SQLite to do so, and have seen ADO.Net and Entity Framework to connect the file to the project. So I guess a few important aspects would be that once I set the database up with the project can I
send the projects back and forth to multiple developers?
who are on different computers who have not installed any SQL
related anything?
And is SQLite a viable solution for this?
I've been trying to get a working solution for about 7 hours now.
I suggest you, use SqlCompact 4.0 instead of Sqlite.
You can download SqlCompact 4.0 from Microsoft download center. Also you can easily transfer database between machines. Read about Private Deployment here. And finally an awesome toolbox for using SqlCompact 4.0 stand alone or addons for Visual Studio