Check with another constructor for htmlView: ContentType mimeType = new System.Net.Mime.ContentType("text/html"); var htmlView = AlternateView.CreateAlternateViewFromString(bodyMessage, mimeType);

You should be able to download an official sqlite3.dll for windows on http://www.sqlite.org/download.html - one developer wrote about this on https://github.com/slodge/MvvmCross/wiki/Sqlite-plugin On the idea of reusing services from mobile apps within server side web apps, Mvvmcross itself doesn't tackle this area - fundamentally the lifecycle and user flow (single vs multiple) is too different for most web apps. Some 'business logic' and 'model' code can be reused across to websites, but much other website code may be better constructed centred around frameworks like nancy, fubumvc, simple web, etc.

You need to implement a custom classloader, something like this Class<?> cls = new ClassLoader() { public java.lang.Class<?> loadClass(String name) throws ClassNotFoundException { byte[] a = read class bytes from known location return defineClass(name, b, 0, a.length); }; }.loadClass("test.MyClass");

This is exactly what I do for many of my projects. Just make sure your library project has all the default set of strings defined in it, otherwise you won't be able to reference them, since the library does not know about the "parent". Then override them in your "parent" projects. You only need to override the ones that are different from default, otherwise it will take the value from the library project. Hope that makes sense. Edit: By the way you can reference booleans like so: <bool name="allow_feature_x">true</bool> and then access getResources().getBoolean(R.bool.allow_feature_x);

Add this to your dependant project's app.config (I.E. the project that has the dependencies on the other projects): <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <probing privatePath="*relative path to assemblies here*" /> </assemblyBinding> </runtime> With 'relative path to assembly here' replaced with the actual relative paths to where the assemblies are built (your new output folder(s)). MSDN

This happens because the Solution file has the Source Control Information in it and the .csproj file will just implement what the solution file tells it. <SccProjectName>SAK</SccProjectName> <SccLocalPath>SAK</SccLocalPath> <SccAuxPath>SAK</SccAuxPath> <SccProvider>SAK</SccProvider> The SAK referes to "Should Already Know" as it pulls the information from the solution file. The solution file should contain something similar to what is shown below GlobalSection(TeamFoundationVersionControl) = preSolution SccNumberOfProjects = 4 SccEnterpriseProvider = {3BA58AB2-18FA-4F8D-95D4-32DDF27D184A} SccTeamFoundationServer = http://TFSSERVER:8080/tfs/DPC SccLocalPath0 = . SccProjectUniqueName1 = Project1\Proje

No it is not necessary REFERENCE ASSEMBLIES(and their dependencies) AND Your PROJECT TARGET the same version. I think you got another issue for could not load project or assembly. Keep in mind 1> Add all assembly which is missing 2> don't run 4.0 targeting project in 2008 or lower (don't run higher version project in lower version SDK)

According to the error, the project was probably made in a newer version of Xcode than the one currently on your machine. Update your software and if it still doesn't work, I'd assume it was made with the newest developer only version, Xcode 5. If this is the case you must purchase a developer account at the: iPhone Developer Center and download Xcode 5. If you do not want to do that, you cannot use the project.

T4 works nearly completely independent from the rest of your code. You're on the right track though, with the assembly directive, but you'll need to specify a full path to the actual DLL of the assembly, unless the assembly is in the GAC (which it probably isn't). Luckily, however, you can use MSBuild macros in T4 directives. So, you'll probably get something like <#@ assembly name="$(SolutionDir)Project.Common.WebApiinDebugProject.Common.WebApi.dll" #> See MSDN for some more background on this syntax. You still also need the import namespace directive. Finally, be wary of project build order. The project that contains your T4 template now depends on Project.Common.WebApi, so you'll need to make sure that Project.Common.WebApi is built first. Otherwise, your T4 template might

Is the project ON a network drive? XAML has issues with projects stored on a network drive. In corporate environments your Documents are often remapped to a network path, causing this problem for the default project folder. Try like c:projectsyourprojecthere instead? WPF Project on a network share with clr-namespace

Tools + Options, Projects and Solutions, Build and Run. Change the "MSBuild project build output verbosity" setting to Normal. Pay attention to the build output, the messages you see after "XapPackager". Which show which files are getting added to the Xap package. Your DLL needs to be in that list. If it is not then your program will fail as described. In which case you'll need to find out why it is getting skipped. Start that by checking that the Copy Local property of the .winmd reference is True.

First, make sure that the Oracle.DataAccess Assembly is indeed in place on the system. It might well be that something failed in your installation process. If it is in place, and you still get the error, you will need to install the Oracle client on this system. ODP is just a wrapper using the client. It will not enable a system without an Oracle client to access an Oracle database as far as I remember.

You can use Add-Type cmdlet: Add-Type -Path "path-to-dll.dll" See: http://technet.microsoft.com/en-us/library/hh849914.aspx

This is a long shot, but are there nested classes with the same name, but different case within the outer class? This will work fine from C#, but since VB is case-insensitive, it will regard those 2 classes as a conflict (and will not provide any intellisense for either).

Under Project Properties » Tool Settings, you could add something like this: -ext ..ExtProjectin$(Configuration)ExtProject.dll It's still a little hackish about constructing the relative path, though. You should still reference the project so that the build order is correct. (The VS team recommends this over Project Dependencies since it works in all build scenarios.)

I have just found a way to add classes to another web project and it worked on my side. First, is to create a .jar file of your main project's classes and add it to your JSFUnit's project properties. You can't create a .jar file for a web project using netbeans IDE, so locate your build.xml from your project's folder and add this: <target name="-post-compile"> <jar destfile="${basedir}/dist/my_web_app.jar"> <fileset dir="${basedir}/build/web/WEB-INF/classes"> </fileset> </jar>

I've found something, not a solution but at least an explanation, and a work-around. The explanation As the ant documentation says: Note that WTP doesn't support IvyDE's workspace resolver. See the details in the page dedicated to WTP integration. The work-around I've created a normal java project and a symbolic link (can be done also on window) to the web-project source folder in the normal project. This way ivyDe can resolve in workspace the normal project and all modifications still "propagate" in the web-project. Not the best way, but at least...hope it may help someone.

Try if possible rebuilding in CS6. I'm trying to resolve a similar random error 'Error #1009: Cannot access a property or method of a null object reference' and I can only surmise that CC is the culprit. If rebuilding in CS6 solves your problem, please let me know!

I'm not sure about your question 1, but if I understand it correctly, you would like to build with Eclipse two Maven projects where A depends on B? Then you may use an Eclipse plugin like m2eclipse. For your second question, I think the solution would be to use the system scope for your dependency that you can't find in any public repository. Of course, if you can deploy the dependency on an entreprise repository it would be better.

Not a direct answer but instead of referencing the dll directly, you should install the Visual Studio extension for SQLite. The extension includes the dlls for all platforms (x86, x64, ARM). It also makes sure that the right dll is used for the platform that you are building for. After you install the extension, it will appear in the references dialog under Windows -> Extensions. Also, when you use the extension, you must change all your project build configurations to be x86 or x64 (on the desktop) or Arm (for Arm devices). It will fail to build if you use AnyCPU.

Is it possible to have a reference to an assembly targeting .net 4.5 in a project that targets 4.0? No. It shouldn't be. There could be some features that are used in .Net 4.5 assembly which are not part of .Net 4.0, In that particular case, it should fail.

You can setup a custom probing path for your 3rd party assembly. Please note that this approach won't work with ASP.NET applications (they don't support custom probing paths).

Not sure if it answers the question the way that you wanted but you could use a CI server such as Jenkins: http://jenkins-ci.org/ and then you wouldn't need to figure out how to create a multi-build .bat script. Each project could still have it's own independent build script and Jenkins can handle building them as a group.

You need to add a reference to the ClassLibrary2 project (asssembly). You will then be able to use namespaces and types in that project. Right-click the other project, then click Add Reference.

Basically you need to do two things: Install maven plugin in eclipse. Add a tomcat server instance in eclipse. This link should guide you to achieve that: http://www.mulesoft.com/tomcat-maven

Go to the directory where you have installed Android SDK. There, go to tools directory. Note down the path of tools directory. Open command prompt/terminal, and cd to tools directory: cd <tools directory path> Run command: android update project -p <path to project directory> -n <name of project> -t android-15 To create a new project: android create project -p <path to project directory> -n <name of project> -k <package name> -a <hello world activity name> -t <android version like: android-15>

gradle.properties: theGroup=some.group theName=someName theVersion=1.0 theSourceCompatibility=1.6 settings.gradle: rootProject.name = theName build.gradle: apply plugin: "java" group = theGroup version = theVersion sourceCompatibility = theSourceCompatibility

It seems that i have misunderstood what requirejs does when it optimizes and creates source maps. It turns out requirejs creates a map and source file for every single JS file in your project as well as a source map for the optimized JS file (typically called main.js). If you're only after a source map for the main.js file then you can delete all the others. Hope this helps somebody else!

I'm assuming that converting all your js files to jsps is not what you're looking for. Obvious solution would be to use a module system (require.js for example) and wrap that value in a module, Something like a jsp with: define({ baseUrl: '<c:url value="/" />' }); which then can be required by other modules. This however might need quite a big reorganization of your code code. A simpler option would be to create a following jsp, included in every page: <script type="text/javascript"> $(document).ready(function () { $(document).ajaxSend(function (ev, jqXHR, ajaxOptions) { var context = '${pageContext.request.contextPath}'; ajaxOptions.url = context + '/' + ajaxOptions.url; }); }); </script> It prepends the con

maven-resources-plugin enable you to copy java source anywhere before compiling (you can initialize phases) but the problem lies in package declaration in the java file. you need to modify it also and that is not simple in maven But why you need to do so ? why you need to use the same code in two different packages ???

This *? indication comes from the git plugin that is shipped with Titanium Studio. It indicates that the file is not commited. To answer your "can't find file" - question, I need to know some more details about your environment (target platform, sdk version, example code, ...)

Standard way in Maven to do this is to provide through dependency and tell maven I need this jar , can you please get it for me. Below is the details that will help you(maven) to identify the jar. <dependency> <groupId>groupid.of.your.jar</groupId> <artifactId>name.of.your.jar</artifactId> <version>version.of.jar</version> </dependency>

Check the .net version in your IIS app pool. Also check the target version in your project properties and make sure you are targeting the same version your IIS app pool is configured for. You should be targeting 4.0+.

The problem lies in the scoping rules of CMake. each add_subdirectory call creates its own scope. Variables declared in such a subdirectory aren't automatically populated up to the parent scope. So the problem is that while RESOURCE_ADDED contains a valid path in the scope of icons/CMakeLists.txt, it doesn't in the root CMakeLists.txt and hence it is an empty variable by the time you use it in src/CMakeLists.txt. To raise the variable up a scope, in icons/CMakeLists.txt you can do: qt5_add_resources(RESOURCE_ADDED ${RESOURCE}) set(RESOURCE_ADDED ${RESOURCE_ADDED} PARENT_SCOPE) There's another slight problem now though! While this will contain a valid value in src/CMakeLists.txt, it points to a file which doesn't yet exist. The qt5_add_resources function must apply the GENERATED so

We are using Eclipse here too and have to handle a workspace with more than 200 plug-ins. Every now and then people have similar problems with their workspace and inconsistencies reported in a weird way by Eclipse. What people here usually do is (next step only in case previous step didn't help): - trying to ContextMenu->Team->Clean/Refresh the whole workspace - creating a new workspace and check out all necessary files from the repository - reinstalling Eclipse to a new directory From my experience after using the Eclipse IDE on a daily basis for many years, it doesn't make very much sense to waste too much time with these issues, unless they aren't solved by one of the steps above. It takes too much time to struggle with these things, while starting from scratch is done in an hour or le

Why don't you do this Right click on Project Root folder > properties > Java BuildPath > Library Tab Check whether any of library is missing (showing error with red cross) if yes then add this library to your project don't forget to CHECK it on Order and Export Do one more thing Right click on Project Root folder > properties > Android > set your Project Build Target check any one target Check your Android-sdk path from Window > Preference > Android

You have several options: 1) Drag & Drop files from one project to the other but without copying them (make sure the 'copy' checkmark is unchecked when importing the files in your project). This will simply link them and editing them on one project will, of course, have the changes to be reflected in the other project. 2) If you're using a version control system like Git or SVN you can link repositories with each other. For example, in Git you can have your main project and link other repositories to it as Git Submodules. This allows you to checkout the changes from all of your submodules anytime they get updated and it also allows you to simply modify the files in your submodules and commit them to the original repository. There are more ways in which you can accomplish what you wa

Thats an interesting question we also face. Currently there does not seem to exist a solution for this problem. The only thing that could come near to providing one is the Mylyn Intent project, as it aims to provide a comprehensive documentation on design decisions, which takes into account the inter-dependencies between plugins. This inter-dependency is exactly the problem. There exist solutions to document the purpose of java packages which is limited to the classes however. Our solution is a readme.textile embedded in the root of each plugin, providing this specific information. It would, however, be interesting to introduce the documentation used for packages for bundle documentation, which could be used to autogenerate an overview documentation.

You have to select the right Compiler for the .cu files Are you following any of the tutorial on how to setup it on visual studio ? http://blog.norture.com/2012/10/gpu-parallel-programming-in-vs2012-with-nvidia-cuda/

Add an entry to your project.clj's :repl-options like the following :repl-options {:init (load-file "src/your-project-specific-file.clj") } If you'd like your functions to be available in all your REPLs, add an entry the user profile in .lein/profiles.clj as follows: { :user {:repl-options {:init (load-file "path/to/file.clj")}} }