I am getting into Excel office add-in dev and trying to get the Woodgrove example (https://github.com/OfficeDev/Excel-Add-in-WoodGrove-Expense-Trends) up and running. Unfortunately, it gives an error when I launch it.
Unhandled exception at line 1, column 1 in https::/localhost:App/Home/Functions.js
.... - Javascript runtime error: 'args' is undefined
Any ideas whether I am missing a setting?
There's a typo in that file. On the very first line, delete the string "args".
In the meantime, I will fix the sample.
Update 3/2/18: You're correct, there was a lot more corruption in that file than just that typo on the first line. I think I found it all and pushed the new version of the file to the repo. It works for me now. If you do a pull now, you should get an uncorrupted version. See if it works for you now.
Related
I am trying to run msbuild command line, but, I am getting in the last step of it, the error below (it is in portuguese, but is the same error in the title.
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Xamarin\iOS\Xamarin.Shared.targets(227,3): erro
r MSB4044: A tarefa "GetMinimumOSVersion" não recebeu um valor para o parâmetro obrigatório "SdkVersion". [E:\2-PROJETO
S\_ALGORIX\Projetos\ACCORD\SOLUTION\AppAlgorix\AppAlgorix.iOS\AppAlgorix.iOS.csproj]
My msbuild command is:
msbuild AppAlgorix.sln /p:Configuration=AppStore;Platform=iPhone /p:CFBundleVersion=1 /p:CFBundleShortVersionString=2.3.1 /p:ServerAddress={mac ip address} /p:ServerUser={mac user} /p:ServerPassword={mac pwd} /p:BuildIpa=true /p:IpaPackageDir="E:\8-IPAS\ACCORD" /t:Clean;Build /p:ArchiveOnBuild=false /p:IsAppDistribution=false /p:CodesignKey="{App ID identifier}" /p:CodesignProvision="{App Provisioning Profile}"
All the {} data are confidential, so I cropped them.
This command was working one day, but I don´t know when, but after some VS 2019 update, the command, stops working.
I have found some articles about it, but I can´t find a way to resolve this problem.
Onw of those articles is this:
https://www.gitmemory.com/issue/xamarin/xamarin-macios/10109/729614745
My VS 2019 is updated in version 16.8.4.
I have here, about 40 apps to build and get the ipa. I was running a dosbat to resolve it, and get those ipas, more quickly. Not having this msbuild command line working, will take me to a big problem, cause I almost every week have some updates in my apps, and build one by one, will not be a great idea.
And one more thing is.. I can build inside VS 2019, without any problem. The problem happens only via msbuild command line.
I used the post Visual Studio update (16.8.1) lead to CI build failures to resolve the error.
"This has reared it's head again in Visual Studio 2019 version 16.8.3.
Looks like they've moved the problem to: \MSBuild\Xamarin\iOS\Xamarin.Messaging.targets I was able to get
my builds running again by removing the _SayGoodbye dependency on line
52 for the _DisconnectAfterClean target."
Although I have resolved the error, now I cant generate the ios.ipa package. Now, I get only the file projectName.iOS.exe, instead of projectName.iOS.ipa.
I dont know if this workaround is the final solution for this bug, yet.
We resolved this by running the build twice in-a-row. (continue on error - ignore the failed first build)
The first time always fails with the error in the question title, but it must somehow sets things up so that the second build has what it needs to succeed. The IPA is generated, etc.
IMPORTANT: DO NOT CLEAN BETWEEN THE TWO BUILDS
I know this solution is a hack workaround, but I prefer it to manually making changes to the .targets files as I have seen suggested elsewhere (those suggestions did not work in our case anyway). Making changes like that without knowing the internals of the build process intimately could result in unintended side-effects.
NOTE: As this solution involves an expected failed partial first build, it does add to the build time, but it was only about a minute or two longer per build, and at least it works reliably.
Hope this is helpful to someone! 🤗
I have a multi-project solution which is backed up by NUnit tests for every subproject. The unit tests are passing for other files. Strangely, for the new item added I am getting BuiltInNUnitRunner.cs not found. Tried to restart the system, ensure the .cs file is available. However, VisualStudio 2017 will not pick up from the call stack frame. The screenshot below for more detail call stack
A little late to this party, but in my case I had a typo in a file path of a process that I was trying to open using Process.Start. It was throwing the error described by #Varun Maggo. I was able to figure this out because, in the Unit Testing Output window, the call stack shown in the error message pointed to the line in question.
So it is probable that the error you're seeing is masking the real issue.
I have an infuriating problem that occurred recently.
Whenever I try to add or rename a file in any of the projects in my solution, or even the solution name itself, I get the following:
Error
TF10210: Source control encountered an error during move
operation: Unable to rename
C:\xxxxxxxxvisualstudio.com\xxxxxxxx -
Rigg\src\xxxxxxxx.Rigg.Domain\Area.cs to
C:\xxxxxxxxvisualstudio.com\xxxxxxxx -
Rigg\src\xxxxxxxx.Rigg.Domain\Area2.cs
Specified argument was out of the range of valid values.
Parameter name: pathLength
(I've replaced the names of mine and the client's company with x'es.)
The thing is, up to last Friday I never had this problem, I've been working on the solution for more than 6 months.
I have not renamed or restructured the solution folder recently.
I've tried deleting the solution folder and getting an earlier checkin from before this happened, with no luck.
I do not get the message if I open the solution in VS2013, which leads me to believe the problem is related to VS2010, and maybe doesn't have anything to do with path length. Unfortunately I can't work on the project in VS2013, as it is MVC3.
Any suggestions?
EDIT:
Solved. I changed the solution's mapping, and it worked. Then I changed it back to the original, and it still worked! I have no idea why this happened, but apparently fiddling with the mapping solved it.
Here we have Dynamics AX 2013 R3 CU8 with the same error:
Team Foundation Server nonfatal error
Specified argument was out of the range of valid values.
Parameter name: pathLength
Can you please describe a bit more detailed how you have fixed the error?
We inadvertently broke VS2010 compatibility in our latest update. We rolled out a fix over night. Let me know is you still hit it. Sorry for the trouble!
I have a weird error when I try to create a new solution in vs2010, it started today...
I get this error no matter what kind of solution I create, and in every directory on the disk:
Any idea about the reason I get this message?
I tried to search the error text on google but I only found posts about errors while converting an old solution file which wasn't helpful.
Also tried running vs2010 as administrator, but nothing works, I still get this message
EDIT:
I checked the space left on my disk (26 GB), tried other names for the solution, tried to create a text file in the folder and it works
One of the most common problems is one or more plugins/addons that either fail them self or fail if loaded in combination with other plugins/addons/vsipackages.
To work out if that is true in this case do the following:
start a visual studio 2010 prompt
type devenv /Safemode
Check stabiity of VS2010
Works? unload/remove plugins until you have a stable installation
Doesn't work? Contact MS Support
The msdn documentation on devenv switches
We use Nant to automate our builds. Everything was working fine until about a week ago when the rains caused our power to go out and the build server had to be re-booted. Now, we get the following error whenever we attempt a build:
<internalerror>
<type>System.Runtime.InteropServices.COMException</type>
<message><![CDATA[SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database.]]></message>
<stacktrace><![CDATA[ at SourceSafeTypeLib.VSSItemClass.Get(String& Local, Int32 iFlags)
at NAnt.Contrib.Tasks.SourceSafe.GetTask.ExecuteTask()]]></stacktrace>
</internalerror>
We ran the Analyze utility on the VSS database and there appears to be plenty of room on the build server, but no luck. Any ideas? I'm at a loss.
My problem was that the current file was empty... I wrote a comment on it and everything worked ok
Ok, here is the resolution. It turns out that somehow, the version of an app.config file that was referenced in the build script was corrupted (all the previous versions, actually), which caused the VSSGet error. Updating the version to the current version fixed the errror.
I had this issue when I tried to migrate a Source Safe database to Subversion, using VSS2SVN.
This error is related to the message
There is a diff chain size mismatch in file '' (bdaaaaaa) at version (versions earlier than that version can no longer be retrieved from the database).
that may be reported by the Source Safe tool analyze.exe.
If you look into the history of the file and try to Get a version that is older than the one reported by analyze.exe, the message of this question is shown.
Microsoft provided hotfix KB927887 for cases where this was caused by XML files toggling BOM inclusion, but I did not try to apply it.
See also Message: SourceSafe was unable to finish writing a file