i have made a UWP build with codename one and am trying to put it on the windows store but i get an error under windows compliance test app manifest
the error is:
Levabo takes a dependency on Microsoft Visual C++ Runtime Package (Microsoft.VCLibs.140.00) framework but is missing the framework dependency declaration in the manifest and Lavabo is the name of the app.
and acording to microsoft what i need to do to fix the error is this:
App manifest must include valid entries for all required fields, please modify the manifest entries listed above. See link below for more information:
but i am not sure where i can change the manifest entries and if it is possible at all.
Codenameone_Setting file:
#
#Fri Jul 01 12:46:38 CEST 2016
codename1.arg.java.version=8
codename1.ios.appid=Q5GHSKAL2F.com.duus.levabo
codename1.ios.release.provision=
codename1.arg.rim.obfuscation=false
codename1.arg.ios.newStorageLocation=true
codename1.j2me.nativeTheme=nbproject/nativej2me.res
codename1.arg.ios.project_type=ios
codename1.arg.ios.interface_orientation=UIInterfaceOrientationPortrait\:UIInterfaceOrientationPortraitUpsideDown\:UIInterfaceOrientationLandscapeLeft\:UIInterfaceOrientationLandscapeRight
codename1.displayName=Levabo
codename1.android.keystoreAlias=
codename1.arg.windows.makeReleaseAppxbundle=true
codename1.ios.release.certificate=
codename1.android.keystorePassword=
codename1.ios.provision=
codename1.arg.android.release=true
codename1.arg.ios.dsym=false
codename1.arg.ios.statusbar_hidden=false
codename1.arg.windows.buildType=Release
codename1.languageLevel=5
codename1.android.keystore=
codename1.vendor=DuusPartnersPS
codename1.arg.win.ver=8
codename1.ios.certificatePassword=
codename1.ios.debug.certificatePassword=
codename1.mainName=MainForm
codename1.windows.certificatePassword=password
codename1.ios.release.certificatePassword=
codename1.arg.ios.prerendered_icon=false
codename1.ios.debug.certificate=
libVersion=116
codename1.arg.ios.application_exits=false
codename1.secondaryTitle=CodenameOne_Template
codename1.description=
codename1.ios.debug.provision=
codename1.arg.j2me.nativeThemeConst=0
codename1.rim.certificatePassword=
codename1.version=1.0
codename1.ios.certificate=
codename1.arg.windows.platforms=x86|x64|ARM
codename1.windows.certificate=/Users/thomaswix/Keychain_1.pfx
codename1.icon=icon.png
codename1.arg.windows.appid=DuusPartnersPS.Levabo
codename1.rim.signtoolCsk=
codename1.arg.android.debug=false
codename1.rim.signtoolDb=
codename1.arg.ios.testFlight=false
codename1.arg.ios.includePush=false
codename1.packageName=DuusPartnersPS.Levabo
Thanks in advance
There were some issues with the the .Net native compiler that caused certification to fail, and sometimes hang. The dotnetnative team worked with me to work around these issues, and I was able to successfully submit an app to the store. Submission should now work correctly.
Having upgraded to Visual Studio 2013, I have found that an old SQL project fails to load when I attempt to open a solution. The error displayed is:
The imported project "C:\Program Files (x86)\MSBuild\12.0\bin\SqlServer.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk. C:\Some\Path\To\Project\Database.sqlproj
In my .sqlproj file I have the line
<Import Project="$(MSBuildToolsPath)\SqlServer.targets" />
which in Visual Studio 2012 resolves to C:\Windows\Microsoft.NET\Framework\v4.0.30319\SqlServer.targets but in Visual Studio 2013 this resolves to C:\Program Files (x86)\MSBuild\12.0\bin\SqlServer.targets. However, the SqlServer.targets file is in neither of these locations.
Presumably this is due to MSBuild becoming part of Visual Studio, rather than it being part of the .Net Framework.
Does anyone know how to fix this issue and to migrate this project to Visual Studio 2013?
Just copied SqlServer.targets from C:\Windows\Microsoft.NET\Framework\v3.5 to C:\Program Files (x86)\MSBuild\12.0\Bin and it helps. VS2013 is now able to open the old project.
I had a similar problem when upgrading from Visual Studio 2008 to 2013.
It took awhile but I had to install the SSDT for VS 2013 (again), then I created a new database project to find out the relative path to the new sqlserver.targets file.
It should be as follows:
<Import Condition="'$(SQLDBExtensionsRefPath)' != ''" Project="$(SQLDBExtensionsRefPath)\Microsoft.Data.Tools.Schema.SqlTasks.targets" />
<Import Condition="'$(SQLDBExtensionsRefPath)' == ''" Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" />
The biggest hindrance that I found to fixing this error was trying to understand the error message provided (BC2014: the value 'database' is invalid for option 'target')
Hope this helps!
I had the same problem and I solved this way:
Just create a file named 'SQLServer.targets' on 'C:\Windows\Microsoft.NET\Framework\v4.0.30319' with the following content:
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<SqlClrTargetsFullPath>$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v10.0\TeamData\Microsoft.Data.Schema.SqlClr.targets</SqlClrTargetsFullPath>
</PropertyGroup>
<Import Project="$(SqlClrTargetsFullPath)" Condition="Exists('$(SqlClrTargetsFullPath)')"/>
</Project>
Good luck.
This can also occur when opening an older project in Windows 10
I had the same problem (SqlServer.targets was not found) when opening an old SQL Server CLR assembly in Visual Studio 2010 on Windows 10, the same version used originally to write the assembly.
Confirmed the same project opened perfectly fine in Visual Studio 2010 on a Windows 7 computer.
Solution
Pay attention to the error message. In my case it was:
The imported project “C:\Windows\Microsoft.NET\Framework\v4.0.30319\SqlServer.targets” was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Simply copy SqlServer.targets from the location indicated in Vladimir Dronov's answer, "C:\Windows\Microsoft.NET\Framework\v3.5\SqlServer.targets", to the directory indicated in the error message.
In my case that was "C:\Windows\Microsoft.NET\Framework\v4.0.30319\".
I had the same problem when trying to build a VS 2010 solution under VS 2013. The fix was to upgrade the solution file to VS 2013 first. After that it worked without further modifications.
The Error Resulting from Several of these Solutions
I posted a specific question (C# VS 2013 Error 02019: Invalid target type for /target: must specify 'exe', 'winexe', 'library', 'module', 'appcontainerexe' or 'winmdobj' CSC) regarding the fatal build error described by Chris Torng below Vladimir Dronov's answer:
Error 1 02019: Invalid target type for /target: must specify 'exe', 'winexe', 'library', 'module', 'appcontainerexe' or 'winmdobj' CSC
The Fix
I was able to get rid of the error related to SQL Server dev tool compatibility issues in VS2013 Community Edition by following the advice in this forum:
https://connect.microsoft.com/SQLServer/feedbackdetail/view/979839
Posted by bsclifton on 11/15/2014 at 7:18 AM
Had this issue too with the Community 2013 edition; Going to Tools->Extensions and Updates and updating "Microsoft SQL Server Update for database tooling" resolved the issue :)
If this doesn't work for you, I'd recommend checking out that forum as it offers up several other ideas for how to fix the problem
Solution 1:
If the project is a .csproj file, you should check if Visual Studio also generated a .sqlproj file while upgrading. If that is the case, you can add that to the solution instead.
Solution 2:
You can try to change the following line in the .sqlproj file:
<Import Project="$(MSBuildToolsPath)\SqlServer.targets" />
to
<Import Project="$(MSBuildBinPath)\SqlServer.targets" />
I've had a good look around and can't see anyone else with the same issue.
I've downloaded the latest install for DNN (via this page https://dotnetnuke.codeplex.com/relea...) and tried to run it as a new install (via visual studio development web server) but the site crashes on the second page of the wizard, I get a javascript error "Invalid character" in the jquery library and nothing happens are that.
Using the VS javascript debugger I can see in the call stack that the error seems to stem from some javascript used to update the progress bar found on the installation page, the line in question is...
var result = jQuery.parseJSON(status);
If I let the code run from here I get a further error of "Unable to get property 'progress' of undefined or null reference" in the same block of javascript code a few lines down...
if (result.progress < $("#progressbar").progressbar('value')) return;
Details of my installation;
Running on Windows 7 64 bit (have also tried a Windows 7 32 bit but get same error).
Using VS 2010
Installing to new (blank) database on MS SQL server 2008
Using a SQL user for authentication
Have tried the suggestion of "unblocking" the zip file before downloading
Given the NETWORKSERVICE user full control over the DNN website folder
I've tried the installation with IE 10 & the latest version of Chrome (30.0.1)
In addition to trying to run the installation using the wizard I also found that you can disable the wizard via this web.config setting;
Running with this I am able to successfully install DNN but when redirecting from the basic wizard page to the DNN site I get an object not set to an instance of an object error on this line...
if (PortalSettings.ActiveTab.PageHeadText != Null.NullString && !Globals.IsAdminControl())
... of the default.aspx code behind
I had a play with DNN 6 last year and didn't have any issues installing so to confirm that was still the case I downloaded the last release of DNN 6 (version 6.0.2.09 from here https://dotnetnuke.codeplex.com/relea...) and was again able to install that version without any problems at all using the same SQL server and running through VS 2010.
Any help would be appreciated.
Thanks,
I was having the same problem and switching the pipeline mode for the application pool to "Integrated" fixed the issue on PortalSettings comming on null on this line:
if (PortalSettings.ActiveTab.PageHeadText != Null.NullString && !Globals.IsAdminControl())
I have just installed the Update 2 for my Visual Studio 2012 Ultimate.
After installing the update and restarting the computer, I am not able to build Windows Phone projects anymore. When I try to build them in VS I always get "The Silverlight 4 SDK is not installed" error.
I have checked, and the SDK is installed. I have also tried by repairing the installation, but nothing. It was working ok befor installing the Visual Studio Update
Does anybody know which is the cause of the problem and how to solve it?
Thanks in advance.
EDIT: I have uninstalled and installed again Silverlight 4 SDK with no result. I have checked the Windows Registry, and realized that there is no entry for Silverlight under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs". Could this be the problem? How do I solve it?
Solved the problem by reinstalling the Windows Phone 8 SDK.
I didn't have this problem in my other computer, so I don't know why it happened.
I have this issue as well when running x64 msbuild. Running the 32-bit version seems to get around the issue.
I just upgraded my machine to Silverlight version 4.0.60831.0 to see if it would help with some Memory leaking issues that I'm seeing.
Now when I try to use WinDbg and attempt to load the SOS.dll I realize that there is no SOS.dll for the .60831 version. I loaded the previous 4.0.60531.0 version, but when I attempt to dumpheap, I get the following error:
The version of SOS does not match the version of CLR you are debugging. Please
load the matching version of SOS for the version of CLR you are debugging.
CLR Version: 4.0.60831.0
SOS Version: 4.0.60531.0
I tried the .loadby command and that was unsuccessful as well
0:028> .loadby sos coreclr
The call to LoadLibrary(c:\Program Files (x86)\Microsoft Silverlight\4.0.60831.0\sos) failed, Win32 error 0n126
"The specified module could not be found."
Please check your debugger configuration and/or network access.
This makes sense because there is no SOS.dll file in that directory.
Is there something I missed somewhere?
Thanks in advance
sos.dll for Silverlight 4 comes with Silverlight 4 Developer Runtime.
http://go.microsoft.com/fwlink/?LinkID=146060
It will download Silverlight_Developer.exe which will contain sos.dll 4.0.60831.0
which is the corresponding developer runtime for Silverlight.