I would like to create subdirectories under the main project
The project structure is:
test1_folder:
test1.pro
core_folder:
core_folder.pro
Headers_folder
Sources_folder
gui_folder
gui_folder.pro
Headers
Sources_folders
Forms (which contains GUI files)
To create gui_folder I know that we should select Application then Qt widgets Application for others I tried all type but it is not working. Can you please help me?
Best Regards,
Related
I am a novice in asp .net Core 3.1 programming. Thank you for your help.
I created three layers for my project, one for the core, one for the database and one for the web.
The models are in the ِDTOs folder. Now my problem is to create database tables. I do not have access to the Category model.
How can I solve this problem? I would be grateful if you could guide me in full detail.
The project error image as well as the dependencies on each layer are present in the image.
Due to the problem of uploading photos on the site, I had to upload them to another site
Images link
https://pasteboard.co/JNeXGKJ.jpg
https://pasteboard.co/JNeXsXs.jpg
Your Category class is in the project Pipeland.Core.
Your project Pipeland.Web references Pipeland.Core but your project Pipeland.DataLayer does not.
At the moment, classes in Pipeland.DataLayer (including PipelandContext) can't access any classes in Pipeland.Core (including Category)
Create a project reference to Pipeland.Core in your Pipeland.DataLayer project.
Then add the line:
using Pipeland.Core.Dtos
to the top of your PipelandContext.cs file.
This assumes that your Category class is in the namespace Pipeland.Core.Dtos, which it might not be, but I expect it is.
I am doing a refactor of my Xamarin project, in which I want to build nuget-packages for my platform specific projects.
And since you can't make your "App.Droid", "App.iOS" and "App.UWP" into nugets I am using class libraries for this.
My problem is when I put my images (ordinary *.png-files) in my UWP-class library it won't work. It is working in both iOS and Android.
So my question is if anyone knows if this is possible, and if so how?
My current setup is as follows:
My UWP-project is named "App.UWP". This is the project i build and the project has the "App.xaml" and "MainPage.xaml".
I then created a "Class library (Universal Windows)" named "Company.Mobile.Core.UWP".
My "App.UWP" is referencing "Company.Mobile.Core.UWP".
I know I have a working connection between the two. My Custom renderers are in the "Company.Mobile.Core.UWP"-project and not in "App.UWP" and is working fine.
Cheers,
Tobias
I have a predefined SQLite database and want to ship it with my App, so I can access it at runtime.
How do I achieve this?
Moreover, I want to Unit Test my app. So far the database file is referenced with the Unit Test Project as basis. Hence, my paths get broken.
How do I test a app like described above?
I've answered to the similar question at MSDN forum. It may help you.
I'm creating UWP app with SQLite.Net-PCL I already have a SQLite db
that I want to use (I do not want to create a new one in the app).
I've copied it to the root of my project folder. How do I access it?
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/b6d7a970-0088-4bd4-aaa8-c86bca4387df/
I have developed a lot of class library projects in VS 2012 to be used in Windows Forms and Web forms applications.
The question is simple. Do I need to deploy the DLL file itself together with the XML file that is created?
For example, the class library project is called DataWare. Upon building, I got 5 files in Release folder (this project reference Entity Framework):
DataWare.dll
DataWare.pdb
DataWare.dll.config
EntityFramework.dll
EntityFramework.xml
I know that ".pdb" file contains debugging information, so there is no need to deploy. The ".config" file is not taken into account. Instead the App.config or Web.config are.
Regarding this, I think I have to deploy just DataWare.dll and EntityFramework.dll.
However, the main doubt is if I need to deploy EntityFramework.xml as well.
Regards
Jaime
The XML file contains the doc comments for the public types & members in the assembly.
You only need it if you want Visual Studio to show documentation in IntelliSense.
If you're deploying a consumer-facing app (as opposed to a developer-facing reusable library), you do not need it.
No, in most cases you do not need it. If there is an external DLL that needs to be copied local and referenced using the config, then you might need to, but that is somewhat rare.
I am trying to create my first Web project and following the demo on the Microsoft Website they show that when a default web form is selected it adds bunch of default folders and files to the project .
I followed it from the start , but "Models" folder is missing in my project solution .
My question is that does "Models" folder contain some classes and files before or if it is missing i can simply create one manually by following the "Add folder" option . Or am i missing a NuGet package ?
Finally, I figured out that if you don't choose the option for signing in to your freshly created web app through individual accounts, that is if you leave it blank , you won't have Models folder in your project, the reason is that when you check the mentioned option, VS will create a class for you called IdentityModels.cs. So, if you want to have folder Models, in the section Change authentification, choose individual accounts.
If you're not using MVC, you may not see the "Models" folder by default in newer VS versions. You should be ok ignoring the models folder and creating classes in root as long as the relevant references are added in your project, for example based on your tutorial, you maybe missing the data entity, data entity design, data entity linq. So for steps you can try creating these classes in root and if the doesn't succeed, try adding these com references. Go to references, Assemblies, Framework, System.Data.Entity, System.Data.Entity.Design and System.Data..LINQ.