I have just installed Visual Studio 2022 community in my PC that has no internet connection.
I skipped the sign in process at the beginning, but I noticed from a few sources that the sign in will be ultimately needed after 30 days of use. Currently I do not have a plan to connect my PC online going forward.
The license page in VS community now shows that the "product key is applied", but does anyone have an idea that this will be enough for me to keep use my VS after 30 days from the installation?
Unfortunately you cannot have a community license without logging-in at least once a month to your Microsoft account (so you will need to create an account if you don't already have one). The following link is for 2019, but it also applies to 2022.
https://learn.microsoft.com/en-us/answers/questions/358527/visual-studio-2019-usage-without-internet.html
For those who are looking for the same solution, it has proven that the sign-in is needed in order to keep use my VS Community after 30 days from the installation.
Related
I have one small doubt regarding Microsoft.Xrm.SDK.dll. Recently I received an email from Microsoft saying they are turning off support for any Microsoft.Xrm.Sdk.dll version less than 8.2.
I am using Dynamics CRM 2016 (App version: 8.1.1.1183, DB Version: 8.1.1.1183), and SDK client to connect to this CRM. This SDK client uses Microsoft.Xrm.Sdk.dll v6.1.
I want to know will it continue to work or do I have to make change in the code and upgrade the dll?
Thanks
This is probably related to ACS deprecation (which is only applicable for online orgs):
See: https://blogs.msdn.microsoft.com/crm/2017/05/29/update-dynamics-crm-client-sdk-version-to-avoid-calls-to-acs/
With the deprecation of Azure Access Control Service (ACS), you should
modify the SDK authentication code by removing all references to ACS.
Effective from Microsoft Dynamics CRM Online 2016 Update 1 (v8.1.1)
and Microsoft Dynamics 365 (v8.2), we removed Live ID support and ACS
dependencies on the server-side. It is required to update the
references in all client side components by updating the SDK.
For custom applications you need to make sure you have the correct version of the SDK.
Custom Application(s) – If you have developed a Web/Windows/Console
application that is interacting with Dynamics CRM
Scan the folders on your server where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, use the table given in the
Team Blog site to determine which version of the SDK you need to
download.
Using the table, determine which version of .NET that you have deployed against, and confirm the version of Dynamics 365 CRM service
you are using. If you are uncertain which .NET version your solution
is using, contact your development or engineering teams.
Once you have determined the correct SDK version to use simply replace the Microsoft.XRM.SDK.dll found in /bin folder with the latest
version of the SDK dll.Replace Microsoft.XRM.SDK.dll with latest
version of SDK dll
I recommend you to go through the MSDN blog
Without knowing when & where (which CRM version your) project started & staying in 2016 now and what’s your future project plans (whether sustenance mode or stay current), could not comment on action.
As a general practice, do a pilot with an upgrade in separate copy/sandbox & see. Then plan for code Update & sdk upgrade in Live.
The VHD specification was made public in 2006. The new VHDX spec was made available in 2012. Unfortunately, all the Microsoft links to it are now dead. Did Microsoft change their mind about making this public? Or, is it just an honest mistake?
It's been hosted on the Open Specifications site for quite some time. As of March 2019 the latest version is 4.0.
The answer is that the link was later provided by Microsoft in a different location.
As of August 2017, it is at https://www.microsoft.com/en-us/download/confirmation.aspx?id=34750
Firstly, please don't reply with the generic advice not to automate Word on a server or a link to the MS web page on "how to automate word on a server if you really must". I am aware of this.
I have a process which runs as a Windows service and uses .Net OLE interop to automate Office (mostly just Open and SaveAs). This code has worked reliably for 8 years on literally hundreds of servers using many combinations of Windows and Office versions, both 32 and 64 bit, so I am happy that the mechanism is reliable. So far...
With Server 2012 R2, it works with PowerPoint and Excel but fails trying to open a word document:
System.Runtime.InteropServices.COMException (0x800A16A0):
The file appears to be corrupted.
at Microsoft.Office.Interop.Word.Documents.Open...
My observations so far which may or may not be relevant:
fails on all documents
works fine in Windows 8.1
the same problem has happened both on a customer site and in our test environment, so is unlikely to be purely environmental
my application is using .Net 3.5
the code is linked against the 2003 Interop assemblies (obviously later office versions are supported by assembly binding redirection)
we have tried it with office 2013 both 32 and 64 bit with the same results, but not tried earlier versions of office
it fails whether the service is running as LocalSystem or as a standard user account
if we run the service process in the foreground (i.e. literally double-clicking on the executable) the problem does not happen
Obviously I still have things to investigate but interested to hear if anyone else has seen this specific problem even if you haven't solved it. Please note there are many difficulties and problems with office automation so unless your symptoms are very similar to mine, you probably don't have the same problem.
Same issues here but got this fully resolved now.
I have a Word 2013 in combination with Windows 2012 R2 Server running in a service process which does everything I want without the need of a interactive session to be started. I use this to convert documents to PDF files. Inside the Windows service I host a WCF service.
Create folders: (replace System32 with Syswow64 depending of you use x86 or x64 bit edition)
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache
C:\Windows\System32\config\systemprofile\Desktop
Last and most important step!
Start - run - dcomcnfg.exe
Open properties -> Component Services - DCOM Config - Microsoft Word 97 - 2003 Document (Note that the version is not mentioned here but that does not matter Office 2013 will use this as DCOM config)
Open tab Identity. Configure the run as a the local Administrator account. I did some tests Word 2013 will work just fine even if no interactive session is started for the user.
We(My Company) are currently facing the same problem, it is pretty much a carbon copy of your problem. We have completed extensive testing around this area and I am now in talks with MS support engineer trying to find a work around.
Unfortunately this is something they don't want us doing, I think they have tightened security on the Windows Server 2012 to stop people from doing this.
What we have tried which should help you:
Server 2012 | Word 2007 | Failed
Server 2012 | Word 2010 | Failed
Server 2012 | Word 2013 | Failed
Client 8.1 | Word 2013 | Failed
Our problem stems from the fact we are running word with a user who isn't associated with the LOCAL system user(i.e. the type of user you have when you are logged into the machine) Windows will just not allow this to happen anymore.
Myself and the MS Engineer are working on "Fooling" windows into thinking it is running Word as a local service, however the MS Engineer said it was a long shot at best and so far everything we have tried has resulted in failure. It's not looking good.
Sorry I don't have an answer for you, but I suppose its good know you are not alone?
I had the same problem with MsOffice 2010 (32bits) and Windows Server 2012R2 (64bits). Word, Excel, Powerpoint don't work with localAdmin.
I created the folder C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache like Andy did and it now work perfectly !
Thanks Andy :)
My service use MS Word for data merging and concatenations functions.
I'm using Word 2016 on Windows Server 2012 R2 .
My log says that Word is opened but when the document is opened is throwed an error.
I've first created all the 4 folder suggested:
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache
C:\Windows\System32\config\systemprofile\Desktop
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache
C:\Windows\SysWOW64\config\systemprofile\Desktop
Only after creating the last directory the problem was solved.
I've not used DCOM config; my application use an user account with administration priviledges; there was no need to use LocalSystem account with "interaction with desktop" options.
Thank you.
We had a working solution for this for quite some time. However the solution broke when we tried to install it on a fully updated 2012 RTM R2 Server. On a 2016 Server we don't see this issue.
In order to make it work again on Windows 2012 R2 Server and also in a none interactive desktop environment:
Follow these steps!:
Actions to solve the issue on a Windows 2012 Sever R2 which is fully updated by Windows update:
Start - Run - mmc comexp.msc /32
Expand: Component Services – Computers – My Computer – DCOM Config
Search for: Microsoft Word 97 – 2003 Document
RMC – Properties – Go to tab: Identity
Set from “The launching user” to “This user”.
Use a “local Administrator account” which has once singed in to the server machine and has opened Word at least once in an interactive desktop.
Last step: REBOOT THE SERVER! And use a new document name to test your solution again.
Like known and said in the other answers these folder need to be created and accessible by the calling user (local system) normally or the user you configure in the prev steps.
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache C:\Windows\System32\config\systemprofile\Desktop
C:\Windows\SysWow64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache C:\Windows\SysWow64\config\systemprofile\Desktop
Thanks for all the help OP and contributors. After creating the INetCache folder it worked out for me. I have done the following to get everything working without an active session(WS2012 R2 / MS Office 2013 64x):
Create a local admin user and log in to setup any printers(printing to file) as well as default word options.
Point the DCOM config identity to the local admin user created.
Create the following file :C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache
For some machines you need to run " mmc comexp.msc /32 " to set the DCOM setting for MS Word. I found that we needed to do this when 32 bit version of Word was installed only.
I've just been going nuts to sort this and have tried numerous solutions. I finally resolved this by changing the Identity to "This User". I then used the account that my app pool ran under and also had to add this user the "Administrators" group..
Phew... hope this helps someone too.
every time i do build to setup project on vs2010 its starts sql manager 2008 process for a while and build. the process takes couple of minutes.
in 2008 it did not do that
any thoughts why ?
G
I don't have an "answer." But I have some information. This (or a very similar) question was asked in how do I stop sql server 2008.... In my case, I had installed VS 2010 (Ultimate) from a Passport drive; SQL 2008 was installed from an ISO image. If I simply plug in the passport drive (VS2010 source) when building the Setup project, the issue "goes away" in the sense that it does not show the dialog. My hunch is that it is still doing the same work, but is finding what it wants (quickly) on the passport drive. If I disconnect the external drive, the problem returns. So if the message is correct and VS 2010 is trying to configure something, it never really gets configured; but it gets past it quickly if it can find its install source.
Someone who has spent more time working with all the configuration pieces might be able to do more with this information.
I created an application in vb.net using visual studio 2010. I want to create an installation file of the application that will not be free with a license so I want to create a trial of 30 jours.if there a way I thank you in advance
3rd Party Option:-
If you are open to 3rd party options, you can check out Crypto Licensing for .NET
Building your own:-
The MSDN - VB Developers Center also has a Shareware Application Starter Kit
You can download this and check this out. This should give you some starting points as well as to how to go about it.
There is also an old channel 9 video of how to use it
Caveat : This seems to be a bit old but it should give you pointers to get you started atleast.