there,
I hope I choosed the right Forum category...
I've uploaded a windows 10 app to the windows store. I've seen that under supported languages is just german, but in my Package.appxmanifest I have
<Resources>
<Resource Language="de-DE" />
<Resource Language="en-US" />
</Resources>
In the Partner-Dashboard I have also german and english in my store entrys..
Thanks for your help!
Chris
The Store listing on dashboard contains two language lists: Languages supported by your packages and Additional Store listing Languages.The Language supported list of the app in the Store is the same as the Languages supported by your packages list in dashboard.
The language shown in the Languages supported by your packages list is the language your package supported. If your project supports multiple languages,not only will you need to add languages in the Package.appxmanifest file (as shown in the code you listed) ,you will also need to add a.resw file for each language in the project.
In your Resource Language list, the first language 'de-DE' is the default language for your project.For more information about this, please see : App manifest language list
After several days of trying to solve this problem, with the help of the Unity people I finally found the answer:
Text edit the Package.appxmanifest file and change from
<Resources>
<Resource Language="x-generate" />
</Resources>
To the languages your game supports.
<Resources>
<Resource Language="en-us" />
<Resource Language="fr" />
<Resource Language="de" />
<Resource Language="nl" />
<Resource Language="pt-br" />
<Resource Language="ja" />
</Resources>
Then edit the vcxproj of your project and before the add this (using the same language codes from before) :
<AppxBundleAutoResourcePackageQualifiers>DXFeatureLevel</AppxBundleAutoResourcePackageQualifiers>
<AppxDefaultResourceQualifiers>Language=EN-US;FR;DE;JA;NL;PT-BR</AppxDefaultResourceQualifiers>
Okay, now just generate the build and send it to the store and all the languages your game supports will appear as expected. =)
Related
I am trying to index tables from our MySQL database on the Solr version that came with our ACF 2016 installation. Adobe's docs state that I need to use Solr's Data Import Handler to do this, which they say entails modifying solrconfig.xml and creating a data-config.xml file.
This does not work as is. Further reading leads me to believe that I need to:
Download a solr-dataimporthandler.jar
Copy ColdFusion's MySQL connector so that Solr can use it
Edit solrconfig.xml to account for these changes
Create a data-config.xml
Am I correct so far? Because I've been trying that, and when I try to reload my collection, the CF administrator gives me an error "Error handling 'reload' action." The Solr admin itself says:
org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: Error loading class 'org.apache.solr.handler.dataimport.DataImportHandler'.
I don't know much about this, but it sounds to me like Solr cannot load one or both of the two jar files I added. If this is the case, then:
What solrconfig.xml should I be editing? I've been working on the one in the specific collection I've set up to index our database to.
Do I need both of those jars? Where should I put them? I have tried them in C:\ColdFusion2016\cfusion\jetty\lib and in a custom lib I set up at C:\ColdFusion2016\cfusion\jetty\multicore\lib.
Some sources (not Adobe) say I need to add lib directives to solrconfig.xml, while others say that any jars in a lib in Solr's "root" directory will automatically get added. I've tried both ways, and get the errors described above.
Still other sources say I need to add them to my classpath. I am hesitant to do this on our server if we do not need to.
I know this question is all over the place, but I have gotten myself quite confused and I would really appreciate any help or pushes in the right direction. My hope is that I am just making some dumb mistakes somewhere, because I don't think it should be this complicated!
Note that Solr itself is running fine and some collections I have set up that index directories of PDFs are working, no troubles. None of the solrconfig.xml files in the other collections have any request handlers or libs referring to data import handlers.
Thanks in advance! I appreciate your reading all of this! :-)
Okay so I finally got it working. As suspected, the root issue was Solr not locating the MySQL connector and data import handler jars. For the benefit of any others who might stumble across this, here is what I did. We are using Adobe ColdFusion 2016 and Solr 5.2.1 that shipped with ACF.
You do need the MySQL connector and data import handler jars. I used a version-matched data import handler called solr-dataimporthandler-5.2.1.jar and I downloaded it from here. Make sure you select the jar file in the "files" section to start the download. For the MySQL connector, I just copied the one that came from ColdFusion. Mine was called mysql-connector-java-5.1.38-bin.jar, and for my CF install, it was located at C:\ColdFusion2016\cfusion\lib.
I learned that Solr will automatically look for jars if they are in a particular place. No need for lib directives or any file editing. For me, I created a folder called "lib" in my Solr instance which is at C:\ColdFusion2016\cfusion\jetty\multicore and I put the jars in there. So the full path to the new jars is C:\ColdFusion2016\cfusion\jetty\multicore\lib, but you do not need to edit any file to account for that.
You do need to edit solrconfig.xml to account for the data import handler. For me, the only way I could get this to work was to edit solrconfig.xml for each collection. Editing any of the various other versions would not work. So for my collection called "dmfile," which I had previously created in the CF Admin, the solrconfig.xml to edit was at C:\ColdFusion2016\cfusion\jetty\multicore\collections\vfs_dmfile\conf. I added the following to the file in the section where the other request handlers were:
<requestHandler name="/dataimport" class="org.apache.solr.handler.dataimport.DataImportHandler">
<lst name="defaults">
<str name="config">data-config.xml</str>
</lst>
</requestHandler>
That's all I needed to do for solrconfig.xml.
In that same directory, create a data-config.xml file. Here's mine:
<dataSource type="JdbcDataSource"
driver="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/myDatabase"
user="myUsername"
password="myPassword"/>\
<document>
<entity name="dmfile" query="SELECT filename, ObjectID from dmfile WHERE status = 'approved'">
<field column="filename" name="filename" />
<field column="ObjectID" name="uid" />
<field column="status" name="dmfile_status" />
</entity>
</document>
To get started, I tried to keep things simple. Note how the entity name matches the name of the collection. I matched the unique ID from our database table (ObjectID) to the standard unique ID field that Solr has (uid). "Column" is the column from our database and "name" is whatever name I want Solr to use. Your database of course will likely be different.
Finally I edited schema.xml, also in the same directory:
<field name="filename" type="string" indexed="true" stored="true" required="false" />
<field name="dmfile_status" type="string" indexed="true" stored="true" required="false" />
The "name" attribute needs to match whatever you set in data-config.xml. Note that I did not add a field for uid -- it was already in schema.xml by default.
I am on a Windows server, so I went to services.msc and restarted the ColdFusion 2016 Add-On Services service. NOTE: restarting ColdFusion itself did not work for me. I needed to restart ColdFusion 2016 Add-On Services, and only that.
Finally I could reload my collection, and (more importantly) I could browse the core in the Solr admin at http://localhost:8989/solr/#/. I could select my dmfile core in the "Core Selector" dropdown, and was able to choose the DataImportHandler without getting an error.
That is how I got it to work for me. I found that I needed to repeat steps 3-6 for every core that I wished to connect to MySQL. Some documentation states that you can do at least Step 3 at a global level, but that did not work for me at all.
Anyways, it took me quite a while to figure all of that out, so hopefully this will help any other CFers out there who were stuck like I was.
When I try to access a website that I built using MVC, I am met with error 500. I contacted my hosting providers and they said the issue was with my web.config file. Problem with that is there wasn't one in the project when I created it through Visual Studio.
I followed this guide to add one: How to: Create Web.config Files. Which is provided by Microsoft.
I'm at a complete loss here as I don't know what sort of info is needed or how to configure it so that it will work.
These are the current contents of the file:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<!-- To customize the asp.net core module uncomment and edit the following section.
For more info see https://go.microsoft.com/fwlink/?linkid=838655 -->
<!--
<system.webServer>
<handlers>
<remove name="aspNetCore"/>
<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified"/>
</handlers>
<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
</system.webServer>
-->
</configuration>
What I'm asking for is a bit of direction as to what I need to do, and why this wasn't included in the website to begin with.
You need to clarify with your provider do they support asp.net core since it has its own runtime library.
Also web.config is related to classical ASP.NET framework not for ASP.NET Core.
Try to create app with any .NET version 4.x in visual studio. Within template you’ll see web.config.
If you still want to use .net core it uses slightly different config mechanisms. You can read more about in www.asp.net tutorial section of asp.net core
Though I've been reading the StackOverflow forums for years, it's the first time I post here. I know the problem I'm talking about has been asked before, but, as I've seen, it seems that there's no clear answer to it, so I'm posting my case as detailed as I can to see if someone can help me understand what I'm doing wrong before I jump off a cliff.
The "Map doesn't work in debug mode" myth: is it true? I've read more than once that, while using the debug API key, the map doesn't load properly, but once the app is released and signed in to the market, the problem disappears... Is this so? May I test a half-functioning app assuming that the map works well and then uploaded it to the market hoping that it will work as expected? (Please, say "yes", and release me from this living hell of tiles that don't load!)
What I've done with my app:
Used the "keytool" command to list the certificate fingerprint of my keystore:
$ keytool -list -alias androiddebugkey -keystore ./.android/debug.keystore -storepass android -keypass android
Created an API project and generated an API key using the certificate fingerprint from the step above.
Added the API key and the permissions on the AndroidManifest.xml:
<uses-feature
android:glEsVersion="0x00020000"
android:required="true"/>
<permission
android:name="com.mycompany.test1.permission.MAPS_RECEIVE"
android:protectionLevel="signature" />
<uses-permission android:name="com.mycompany.test1.permission.MAPS_RECEIVE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
(...)
<meta-data
android:name="com.google.android.maps.v2.API_KEY"
android:value="AItaSyDGE2yil3tCr9NP45QVDPfmRUP-gNv7uLY" />
Added a map on the XML layout of my activity:
<com.google.android.maps.MapView
xmlns:android="http://schemas.android.com/apk/res/android"
android:id="#+id/mapView"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:enabled="true"
android:clickable="true"
android:apiKey="AItaSyDGE2yil3tCr9NP45QVDPfmRUP-gNv7uLY"
/>
<!-- Though the Google page says to use the following code, Eclipse shows an error referring to the "xmlns" tag and it can't be compiled: -->
<!--
<fragment
xmlns:android="http://schemas.android.com/apk/res/android"
android:id="#+id/map"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:name="com.google.android.gms.maps.MapFragment"/>
-->
I've tried compiling in the emulator using Google APIs, using Android 4.x, using three real devices with Android 2.3, 4.0 and 4.2, exporting the project's .apk and installing the APK on the device directly from the USB card, but the behavior is always the same: when trying to show the map, LogCat fills with the following error:
IOException processing: 26
java.io.IOException: Server returned: 3
at android_maps_conflict_avoidance.com.google.googlenav.map.BaseTileRequest.readResponseData(BaseTileRequest.java:115)
at android_maps_conflict_avoidance.com.google.googlenav.map.MapService$MapTileRequest.readResponseData(MapService.java:1473)
at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher.processDataRequest(DataRequestDispatcher.java:1117)
at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher.serviceRequests(DataRequestDispatcher.java:994)
at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher$DispatcherServer.run(DataRequestDispatcher.java:1702)
at java.lang.Thread.run(Thread.java:856)
Anybody knows what can be happening? I've followed the Google guide like a thousand times, regenerated my API key, checked my manifest, tested the app on the emulator, on devices, etc. and NOTHING changed anything! As I've said previously in this post, I've read that the maps are, simply, not able to be tested when "testing" the app, so one should wait until the app is published in the market to see them working... However, it sounds me weird! Any ideas?
Thanks in advance for your time and effort! :)
I am trying to add a JSON endpoint to a WCF RIA Service.
I have read many tutorials on this and I have also watched videos on silverlight.net.
Everywhere I find something on this topic, I am told to use the domainService Tag in web.config.
One code example looks like this:
<system.serviceModel>
<domainServices>
<endpoints>
<add name="JSON" type="Microsoft.ServiceModel.DomainServices.Hosting.JsonEndpointFactory, Microsoft.ServiceModel.DomainServices.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
</endpoints>
</domainServices>
<system.serviceModel>
This is not working and there are two issues:
In Visual Studio 2010 the domainService Tag is underlined blue, with the hint, that this is an unexpected tag.
In IIS the domainService Tag is producing an unknown element error.
Among others, I have referenced the following DLLs in my web project:
-Microsoft.ServiceModel.DomainServices.Hosting
-Microsoft.ServiceModel.DomainServices.Tools
-Microsoft.ServiceModel.DomainServices.LinqToSql
-System.ServiceModel.DomainServices.EntityFramework
-System.ServiceModel.DomainServices.Hosting
-System.ServiceModel.DomainServices.Hosting.OData
-System.ServiceModel.DomainServices.Server
I also have the WCF RIA Services V1.0 SP2 installed.
I really don't know, how to resolve it. I need help. I have googled and searched excessively.
Thank you.
This case is solved. Please read my comments to Jeff's answer. You may find some additional information on this problem.
The JSON endpoint is part of the WCF RIA Services Toolkit, not the product itself. You can get the Toolkit MSI here:
http://www.microsoft.com/en-us/download/details.aspx?id=26939
However, I recommend pulling the JSON endpoint in through NuGet instead, using the RIAServices.Endpoints package:
http://nuget.org/packages/RIAServices.Endpoints
Here's some more information about the NuGet packages available:
http://jeffhandley.com/archive/2012/12/10/RIA-Services-NuGet-Package-Updates-ndash-Including-Support-for-EntityFramework.aspx
For me the correct way to resolve the issue was adding the following to web.config
<configuration>
<configSections>
<sectionGroup name="system.serviceModel">
<section name="domainServices" type="System.ServiceModel.DomainServices.Hosting.DomainServicesSection, System.ServiceModel.DomainServices.Hosting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" allowDefinition="MachineToApplication" requirePermission="false" />
</sectionGroup>
</configSections> ...
Is there a way to factor out and parameterize repeating parts of Logback XML configuration? I have many different rolling file appenders configured basically the same except for the file names. I use that in conjunction with a bunch of loggers with their 'additivity' turned off so I can redirect different parts of the stack to different files. This adds up to a cumbersome and long configuration file composed of many almost identical segments.
I've used Logback's <include> feature before, but it doesn't address this reuse issue since I can't parameterize the included configuration. I'd expect such a feature to look something akin to:
<include resource="file-appender.xml">
<property name="filePath" value="/where/logs/go" />
<property name="baseLogger" value="com.mycompany.thatpartofthestack" />
</include>
But as far as I understand that's wishful thinking. Is there another way of factoring out Logback's configuration via templates, macros, functions or whatnot?
Try using variable substitution in local and/or context scope.
Perhaps the easiest way is to define variables in some resource file, say logback.properties bundled with each each application. Moreover, each application would carry a logback.xml file importing logback.properties.
<configuration debug="true">
<property resource="logback.properties" />
<!-- set root level as given by the value of the root.level variable -->
<!-- if root.level is undefined default to DEBUG -->
<root level="${root.level:-DEBUG}"/>
</configuration>
If you wish to set the root level to WARN in webapp-A, simply add the following line in logback.properties file bundled with webapp-A.
root.level=WARN
You can bundle logback.xml as a resource in a artifact common to your various applications.