I am using SqlGeography in a project that was working but now is not. The only thing that has changed that I can think of is that Windows 10 did an update to my PC but I am unsure that that is the source of the problem.
I used NuGet to remove and then re-add the reference to SqlServer140.dll and got this message:
Errors were detected when processing \packages\microsoft.sqlserver.types. 14.0.1016.290\nativebinaries\x64\SQLSERVERPARTIAL140.dll. Please make sure that the file eis accesible, and that it is a valid assembly or COM component.
I used this SO thread to work on this problem. I downloaded Dependency Walker and ran it against SqlServerSpastial140.dll and got this error message:
Errors were detected when processing that . See the log window for details.
Unfortunately, the help file for Dependency Walker is not included in the download (I downloaded both form its home page and also a link at Microsoft - the help was missing from both) so I do not know how to read the result. Here is an image of the result:
Assuming the "log window" is the one at the very bottom, it is not helpful. What do I have to do to restore the SqlGeography functionality. I've also tried other suggestions from the link mentioned above but nothing has worked.
What worked for me was to go to this file location below and copy the SqlServerSpatial140.dll to my project bin folder.
C:\Users<user>.nuget\packages\microsoft.sqlserver.types\14.0.1016.290\nativeBinaries\x64
Related
To resolve this issue I got there to the link provided by vscode
https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Ok, this, corrects the error, But when I restart the Linux and again open my React project,
I get the Same error.
max_user_watches file again gets the value of 8192 as no. of max files.
My react server is not starting due to this issue.
Then I again follow the same step of the link provided, this sometimes gets frustrating.
Any permanent Help I could get from you.
A workaround:
Just disable this built-in extension: TypeScript and JavaScript Language Features
I built my windows8.1 silverlight app with vs2015.
while submitting to store its complain as "Package acceptance validation error: WMAppManifest.xml wasn’t found" tough it exists.
Local windows app certification kit complaining that there is an error in reading this file.
also looked into below post, MY wmappmanifest schema looks correct
AppManifest Validation failed. Invalid AppPlatformVersion in WMAppmanifest.xml
Could you please help me in figuring out the issue here? you help is highly appricated.
My silly mistake. After editing xap file, while creating zip file creating folder inside folder. It is fixed now.
Its a .NET 3.5, x86 application that I built. It works. But when I try to install it using a custom installer, it fails with this error The App has stopped working. In the dialog box, it shows path to two files. In one of the files, I found this.
<ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>app.installer.exe</Parameter0>
<Parameter1>1.0.0.0</Parameter1>
<Parameter2>5321e224</Parameter2>
<Parameter3>App.Installer</Parameter3>
<Parameter4>1.0.0.0</Parameter4>
<Parameter5>5321e224</Parameter5>
<Parameter6>4</Parameter6>
<Parameter7>e</Parameter7>
<Parameter8>System.IO.FileNotFoundException</Parameter8>
</ProblemSignatures>
Is there a way I can find what file was not found for Parameter8 above?
In the other file, I found this Exception Code: 0xe0434f4d but that didn't help much either.
Update:
I'm installing by adding a separate project that is pointing to the .application file of the actual app like below.
try
{
Uri deploymentUri = new Uri(deployManifestUriStr);
iphm = new InPlaceHostingManager(deploymentUri, false);
}
It was missing a dll. I tried copying that dll to the folder where exe was being run from and it works. But I couldn't still figure out how to find the NAME of the missing file. I just found out it was missing a dll by trial and error.
Unless I get a better answer, this is the answer, I guess. Make sure you have all dlls the exe is expecting in the exe directory.
I am trying to import DebugKit and CakePHP is producing the following error: DebugKit.ToolbarComponent could not be found.
Right below it, it says:
Create the class ToolbarComponent below in file:
/Users/SomeUser/Sites/SomeProject/app/Plugin/DebugKit//Controller/Component/ToolbarComponent.php
If you notice though, there are two slashes between DebugKit and Controller for some reason, and that's obviously not a real directory. The server running PHP 5.4.17. I have followed the exact installation instructions listed here. Any suggestions?
I had the same problem and solved it by changing the permissions to 755 to folders within DebugKit.
When I encountered this problem, I realized I had a Plugin/DebugKit folder structure in my project's root, and under the app directory. The one under app was empty, save for a blank file called empty. Strange. I have no idea how this happened. (Perhaps from accidentally running composer as non-root?) I deleted app/Plugin/DebugKit, and moved the one from the project root into app. No more error.
DebugKit does not currently seem to be compatible with cakephp 3.0 even though it is the example in the documentation.
The latest version still seems to use the 2.x methods.
I will also submit a ticket regarding this to update their documentation to prevent confusion.
If there is something I missed regarding this issue and it is actually possible to install this, let me know.
I'm starting an SL project in VS2010, and I'm finding that the AppManifest.xml file isn't being updated by the build. This causes the xap to fail to load in the browser, throwing an InitializationException. Doesn't VS maintain this file for you?
I noted that the Build Action listed for the AppManifest.xml file is currently "None", but I'm not sure what I should change that to, if anything.
The problem turned out to be that I didn't have any Application class in my project, nor the required App.xaml. (I had somehow deleted these files when attempting to customize the solution.) This caused the xap to fail to load, and the error message led me to believe that the root cause was the AppManifest.xml, which generates the AppManifest.xaml file.
This was a mistake. Fixing the Application class and the App.xaml solved the problem.