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.
Related
Recently I've been unable to load javascript scripts to my webworkers in react for some reason. It always responds with index.html.
My config is simply a standard create-react-app app. The screenshots are from my actual project but I have confirmed that the problem persists if I create a new project and try to initialize a minimal example.
Each ffmpeg.* file is affected. This is also not specific to ffmpeg since another library had the same issue - thankfully the initialization of that library is simpler so I was able to simply put that libraries worker-file in the public folder - and that worked.
It might be a stupid question but I'm really at my wits end here and I can't figure out how to investigate further.
Thank you <3
EDIT:
It works if I put all the files it is trying to hit in the public folder - so it has to be some kind of context issue(??) This seems like a really stupid way to go about it. It's not in a worker at the point of loading - it's the worker loader that fails to access the stuff it needs in the node_modules folder, (core script, worker script and wasm code). Whet?
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
I have been programming on a winforms project for about a month days. Recently one of the form designers always show an error page.
When the project is just loaded on VS, there's no error. After I do some modification then rebuild it will show the error page of:
The component 'LiveCharts.Wpf.DefaultLegend' does not have a resource identified by the URL '/LiveCharts.Wpf;component/defaultlegend.xaml'.
and the call stack shows:
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
at LiveCharts.Wpf.DefaultLegend.InitializeComponent() in c:\Users\btord\Documents\Projects\LiveCharts\WpfView\DefaultLegend.xaml:line 1
at LiveCharts.Wpf.Charts.Base.Chart..ctor() in c:\Users\btord\Documents\Projects\LiveCharts\WpfView\Charts\Base\Chart.cs:line 82
at LiveCharts.Wpf.CartesianChart..ctor() in c:\Users\btord\Documents\Projects\LiveCharts\WpfView\CartesianChart.cs:line 40
at LiveCharts.WinForms.CartesianChart..ctor() in c:\Users\btord\Documents\Projects\LiveCharts\WinFormsView\CartesianChart.cs:line 46
at Controls.Chart.MyChart.InitializeComponent()
at Controls.Chart.MyChart..ctor()
I checked the path but found no 'c:\Users\btord' directory and a few days ago I moved my Documents directory to D driver.
Sometimes after I build on release it will show another error page of:
Could not load file or assembly 'LiveCharts.WinForms, Version=0.9.6.0, Culture=neutral, PublicKeyToken=0bc1f845d1ebb8df' or one of its dependencies.
And there's no error in source code of the designer at all, neither when building. The execute file can run healthily.
It seems to commonly happen when multiple copies of live charts dll's are present in a solution build.
For me it was used both in the main executable and a plugin class library building in a sub folder. The effect is two copies of the Live Charts dll's in different folders which it doesn't like.
Packages.config
If using a packages.config file to handle references you can set the LiveCharts references to "CopyLocal"=false for the extra projects. This stops multiple copies of the dll's being included the build. It will happily use the copy loaded in the main project.
Package References
Sadly there isn't an option to not copy the files when using the newer style package references.
Removing extra copies post build seems the easiest workaround I've found.
In Project Properties, Build events page, post build event command line box add
del $(TargetDir)LiveCharts.*
$(TargetDir) is your projects output path.
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.
When I compile my Silverlight prjoect changes aren't made.
And when I create a new Project no xap file is generated. neither in clientbin nor bin debug/release.
I cleared cache ...I tried different browsers. Nothing works
i figured out myself.
in vs2010 on options->projects and solutions->build and run->On run, when projects are out of date it was set to never build.
i have no idea how that was done because i never changed anything there.