After opening website in VS2017 - Error Publishing Customization - visual-studio-2017

I am relatively new to Acumatica. I have been following the Development series of training videos and hit a hard stop on T300 video 4 after opening the website in Visual Studio and then trying to publish the changes in my customization project (after detecting/updating changed files).
Error:
The CodeDom provider type "Microsoft.VisualC.CppCodeProvider, CppCodeProvider, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" could not be located.
My environment is pretty simple:
Acumatica ERP 2018R1
Visual Studio Community Edition
Windows 10 Pro build 1803
I found a number of posts suggesting that I install a nuget package, which may or may not have helped but did not fix the problem. (Microsoft.CodeDom.Providers.DotNetCompilerPlatform)
I stumbled across a reference to the node_modules folder (sorry, lost that post link) which prompted me to check my TST vs DEV instances, and I found it does not exist in my TST instance. I also then noticed that the error I received during publishing happens after a series of lines about node_modules.
After a little more digging, I found https://stackoverflow.com/a/43494775 which seems to have stopped the node_modules folder from being created and appears to have solved my problem publishing inside of Acumatica.
Other posts for visual studio claimed that the issue comes from the C++ compiler not being included in GAC in VS2017, but I completed the T100 and T200 courses on VS2017 without any issue. The problem seems to be connected specifically to opening the Acumatica Website in VS2017.
Does anyone have any experience with this issue that can confirm disabling NPM restores won't cause me headaches down the road? Or is there a better solution? I don't recall anything in the setup guides telling me to make this change, and I haven't found any references that this was an issue before VS2017.

I do recall running into this in older version of 2018R1.
These posts helped me solve the issue:
This post solved it for me:
How can I disable NPM package restore in Visual Studio 2015?
Also with help from this post:
Getting File Path error while adding file to files list in Customization Manager
if you still have the node_modules related folder just delete it and you should be good (from what I can remember).
If these don't work try the latest 2018R1 build. (or at least 2018R1 Update 1)

Related

VSTS feed "refresh" mechanism in Visual Studio

I have set up a VSTS nuget feed. And I have pushed some packages two days ago. I was able to add those packages to my project. But I needed to push an other version for one of them. Made new nupgk version, pushed it and I can see it in VSTS, I can download it from there, Visual Studio 2017 is also listing it correctly but when I try to install it, I am getting an error:
Package 'whatever 1.0.1' is not found in the following primary source(s): 'https://whatever.pkgs.visualstudio.com/_packaging/feedname/nuget/v3/index.json'. Please verify all your online package sources are available (OR) package id, version are specified correctly. 0
What I have tried:
- waiting around 10 minutes
- restarted Visual Studio several times
- pasting the above url into a browser and refreshing it manually several times
One or more of these helped. But I would like to know if there is any canonic solution for that.
I used the answer widget to have some formatting. Still, this might not be "the" answer, as I don't know the mechanism beyond. But it looks to be a workaround.
Steps:
Create a solution with a library project (let's call it L01)
Add another library project to the solution (let's call it D01)
Make a nuget package from L01 (version 0.0.1)
Push the package to your VSTS feed
Manage packages for project D01 and browse your feed
Package L01 v0.0.1 will be listed
Add it to project D01, it will work
Edit L01 nuspec file and change version to 0.0.2
Build and push the new package
Go back to project D01 and refresh the package list. The update will be shown.
Try to update. It will fail with the error message from my question.
Now go to folder %localappdata%\NuGet\v3-cache (or equivalent)
Locate the folder corresponding to your feed and open it
Locate list_l01.lib_index.dat (where l01 is the package name) and delete it
Go back to project D01 and try to install the update. It will succeed.
Would be good if others could confirm. I have reproduced this several times.
Seems you are trying to download the package or packages that where just freshly pushed to VSTS nuget feed.
Since Visual Studio 2017 is listing it correctly, then the issue should not related to the feed on VSTS server.
If this occurs very recently(download the new refresh package) and your package is very large, this maybe a network delay. Suggest you use a fiddler trace when this issue happens again. This makes "some" sense, what you see is probably an incorrect propagation of pushed packages showing up in the search results but not yet available to download.
And some other also encounter the same issue and error as you.
FYI, I've been seeing this exact issue in the past month or so.
Switching between sources, uninstalling and reinstalling are some work
arounds, but not 100%. Pushing my own packages up to VSTS and then
it takes like 15 minutes to finally get it to install.
More details please take a look at this similar issue Package update not found when updating via Visual Studio Solution

Can't get past Microsoft.VisualStudio.MinShell.Msi.msi in VS2017 RC Update

I previously successfully installed Visual Studio 2017 RC Enterprise on Windows 10 Home. I saw in the Notifications area an update to a later version of the RC, and so I clicked on that notification to install it.
The installation got as far as the attempting to install the Android Emulators, but failed and the log said it needed Win10 Pro.
So I removed the emulator from the install options, but the install didn't complete and this time the log said:
[27ac:0038][2017-01-31T10:08:47] Download requested: https://download.microsoft.com/download/8/7/A/87AEAAB0-D624-400E-899E-61FAFAE42BA5/Microsoft.VisualStudio.MinShell.Interop.Msi.msi
[27ac:003a][2017-01-31T10:08:47] Attempting download 'https://download.microsoft.com/download/8/7/A/87AEAAB0-D624-400E-899E-61FAFAE42BA5/Microsoft.VisualStudio.MinShell.Interop.Msi.msi' using engine 'WebClient'
[27ac:0026][2017-01-31T10:08:48] Completed: Installing Microsoft.VisualStudio.MinShell.Msi
[27ac:0026][2017-01-31T10:08:48] Error: Package 'Microsoft.VisualStudio.MinShell.Msi,version=15.0.26109.1' failed to install. MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.MinShell.Msi,version=15.0.26109.1\Microsoft.VisualStudio.MinShell.Msi.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL="7" VSEXTUI="1" VS7.3643236F_FC70_11D3_A536_0090278A1BB8="C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise" , Return code: 1316, Details: The specified account already exists.
I tried to follow the instructions from Visual Studio 2017 RC Install Error "The specified account already exists." however its says the action is only valid for installed products
Yesterday I did notice MinShell in the Programmes Uninstall list and tried removing it from there.
However it makes no difference and every time I try and run the installer I get the same error. I have tried making sure that no VS2017 related items are installed in Programs and Features, and deleting directories manually from Program files etc
Starting to get really annoyed as I had a completely working compiler and IDE and I've already been totally unable to upgrade Win10 to the Anniversary Update due to the 0x8007002C – 0x400D error during Migrate-Data operation. I tried the fix of resetting the Storage app to make all defaults C:, and then the Documents link, but that didn't fix it, although I see I've missed Downloads, Pictures and Video, so will try again tonight but I still don't see it working, although I think the failure moved from 79% to 83%
#Peter Nimmo I had the same issue. Solve it by:
Go to C:\Program Data\Microsoft, go to Properties then click the Security tab and add System, then give full permission. The reason why it couldn't install is because it can't access the folder required.
Hope it works for you. If it doesn't, you could try the following additional steps:
Go to C:\ then at the search box type %temp% then delete everything in it.
Run this script in Powershell Admin mode: https://gist.github.com/heaths/77fbe0b44496960fab25c2eb0b9e8475.
This problem might be caused by setting a separate cache folder when installing. The steps below should fix it.
delete the visualstudio folder in your Registry editor HKEY_LOCAL_MACHINE\SOFTWARE(under Microsoft?)
run InstallCleanup.exe---> C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout
delete contents in your temp folder C:\Users\yourusername\AppData\Local\Temp(skip items that cannot be deleted)
run InstallCleanup.exe
inside C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout
then restart your computer
Go to %ProgramData%\Microsoft and rename VisualStudio folder (e.g. to VisualStudio_old)
Try again with fresh install.
Please temporarily disable 3rd party anti-virus software and try the following steps to check if it works for you:
Type “Administrative Tools” in search box
Open “Local Security Policy”
Navigate to “Software Restriction Policies” (If it displays “No Software Restrictions Defined”, please right-click on the “Software Restriction Policies” node and select “New Software Restriction Policies”)
Double-click on “Enforcement”
Select “All users except Local Administrators” and click on OK
Restart your computer and run the Visual Studio Installer as administrator to repair the installation
Please Refer : https://learn.microsoft.com/en-us/answers/questions/147767/visual-studio-2019-can39t-install-microsoftvisuals.html
similar error for me sort of, it starts installing then gets stuck on shell(minimum) and shell interops and the shell(minimum) resources and interop resources..then i get a fatal error, tells me that Visual Studio Devenv resource fails.. no matter what i try i cannot install on my windows 10 1607 anniversary update 3 64-bit with all updates to this minute. I read microsoft is aware and its become a huge problem, programming error. Anyone figures out how to install let me know please.
EDIT: so its a huge pain to get visual studio 2015 to install, i kept reinstalling it and everytime the error window came up i read the log, then i manually searched and installed components listed, and also had to manually create folders almost each time following the path listed in the log file. after 12 hours and alot of searching and installing i now have a fully functional visual studio 2015 pro edition back on my computer..i wanted 2017 but thats even worse to install..lol..

VS2017 RC1 Installation installation error - Microsoft.PortableLibrary.TargetingPack.Msi failed - No XAML

I had errors installing VS2017 with
Package 'Microsoft.PortableLibrary.TargetingPack.Msi,version=15.0.26004.1' failed to install
The actual IDE will open but I don't have any XAML functionality - it appeared to fail the installation before this component was installed. XAML files won't load and there is no XAML listed under 'Text Editor'.
How to fix this error?
After several hours finally managed to get it to work:
Still not sure exactly what a targeting pack is - and why VS couldn't install it but I manually installed this package and managed to get it to work:
Manually installed:
Microsoft .NET Framework 4.6.2 Developer Pack and Language Packs
https://www.microsoft.com/en-us/download/details.aspx?id=53321
Other things I did that may have contributed to the solution:
I rebooted
I removed all files in C:\ProgramData\Microsoft\VisualStudio\Packages - actually I moved them to an OLD folder and later deleted them. You will see packages downloaded here after you restart the install.
I had previously created a symbolic link from %ProgramData%\Package Cache to another drive to save space (https://superuser.com/questions/455853/can-i-delete-the-folder-c-programdata-package-cache). This symbolic link didn't seem to work anymore leaving me with some files in %ProgramData%\Package Cache and the rest in the other drive. I moved them over and recreated the link. If this is something you did to save disk space and forgot then that could contribute towards a failed solution.
Something above fixed the issue and I now have XAML back again.
Note: The VS2017 RC1 does not support offline installation so that was another avenue I explored and gave up on. The command line switches currently do NOTHING.
I believe the package I needed is the following one but not absolutely sure.
C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.PortableLibrary.TargetingPack.Msi,version=15.0.25719.0

Can't run VS 2015 Community without /resetsettings; Getting CANTLOADLIBRARY on opening new projects, and crashing on new .cpp files

I have Windows 10, fully updated.
I downloaded and installed Visual Studio Community 2015 last week for the first time, (previously programmed in Code:blocks, still installed) and selected custom install to allow for C++ and Python programming.
Installation ran smoothly, but VS always fails on launch.
On first launch ever, it said it was setting things up for first startup; asked me for sign-in which I did, at which point it briefly showed something about my profile before saying 'An error occurred while starting for the first time. Please restart Microsoft Visual Studio'. Imgur images of all dialog boxes here, including parts of a processmonitor log I estimated to be around the general time of the error.
Closing and restarting several times didn't help.
Uninstalling and re-installing didn't help.
Rebooting didn't help.
And uninstalling, running Ccleaner's Cleaner and Registry Cleaner, rebooting computer and re-installing VS didn't help either.
Repairing the install from Programs also didn't help.
I managed to find the exact same error on Google Search for VS 2013 but the only solution was where one person got a completely new OS and re-installed VS on that.
I tried the other suggestions they had including running:
devenv.exe /safemode
devenv.exe /resetskippkgs
devenv.exe /resetuserdata
devenv.exe /installvstemplates
devenv.exe /resetsettings
the first 3 took me to the same sign-in screen. Regardless of signing-in or not, or running VS from the Administrator Profile or not, these option always give the same failed on first startup error.
Installvstemplates gives an error saying the operation could not be completed, but /resetsettings finally got me into VS.
That's about all it does though, I can go to the home page and access options/menu buttons, but signing-in makes it crash and reload again (but it does sign me in and take me to the home screen)
Signed-in/not and Administrator or not, VS crashes on opening a new .cpp file.
When I click Start a New Project I get "Error loading type library/DLL.(Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)). Closing VS and trying to open it normally from start menu still always throws the original error, despite working if I open it via /resetsettings.
I've also checked [HKEY_CLASSES_ROOT\CLSID{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\InProcServer32] in Regedit and found it is apparently correct.
I also used devenv /log to generate an xml file of the process when I open it.
Just to mention I have .NET Framework 4.5-4.6 installed with VS as well.
Looking forward to any advice.
So, for anyone else getting the same problem, I haven't gotten any other advice, since this post.
If you're still having probs # this point the only real solution seems to be a clean install of your OS .
I can confirm it solved all my issues, with VS + some OS problems I wasn't aware of . I can only assume they might've been related, good luck.

VS2010 Intellisense problems

This question actually is an implicit answer, since I could fix the problem in the meantime for myself. But I wanted to publish my experience, since some other developers might have a similar problems.
The problem:
I am using VS2010 prof SP1 on Windows XP SP3, pure C++ only. (AntiVirus software present).
Since some days Intellisense - which is quite helpful under normal conditions - does not work anymore.
Things tried:
created a new simple console application. -> Intellisense still not working.
resetting VS-Settings by means of Tools/Import & Export Settings/Reset. -> Intellisense still not working
Changes to option settings in Text-Editor/C++/Advanced inclusive logging did not help.
-> Intellisense still not working
There was actually an interesting observation:
Intellisense normally creates a directory 'ipch' in the solution directory to store intermediate files. In my solution folders it disappeared as soon as the solution was opened. When I created a folder 'ipch' and opened the solution Intellisense removed the folder again - strange.
The final fix:
During the last week some new Windows updates were installed. I noticed some other unusual behaviour of my PC as well. After having created an image of my PC, I decided to
uninstall Windows updates from 2013-09-11 (4 packages) and one update from 2013-08-28.
(unfortunately I did not note down the KB-numbers)
AND: out of a sudden Intellisense is working again !
Maybe this report could be helpful for some other persons.
Automatic Updates are now disabled on my PCs.
Confirmed 100%
Microsoft Visual Studio 2010 Version 10.0.30319.1 RTMRel
Microsoft NET framework 4.0.30319 RTMRel
Microsoft Windows XP Professional Version 2002 Service Pack 3
Intellisense stops working after installing KB2876217.
Intellisense is back after removing update.
I had the same problem and also had the idea that one of the Windows Updates is buggy, so I can confirm your report.
I tried to uninstall them one-b<-one and found the "bad guy":
KB2876217 destroys intellisense for VS2010 under XP SP3.
A supported hotfix is available from Microsoft to fix this issue. Check at http://support.microsoft.com/kb/2526044/en-us
Actually, it may not be such a good idea to uninstall update KB2876217. Instead, install Visual Studio SP1 update (if not already installed) and then install update KB2526044. I have tried it before and it does work...