In my project we are using many crystal reports files(rpt), when we are compiling my application showing error like No disk space error so now i want to divide crystal reports into separate project.
How can i do this as separate project , when how can i take a reference in main project.
Although I have not separated out my Crystal Reports from any of my projects it does appear doable according to this SO thread.
To do this you would create a new solution. Then create one project for CR reporting and add your exisiting one that contains your business logic. You can then reference your reporting project within your business logic project.
hmk - Please let me know if this works as I might have to do this myself in the near future!
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 trying to learn about the MVC structure of Asp.NET core MVC.
Therefore, I am trying to build a small web app similar to the ecommerce system 'simplcommerce' whose code is open source.
My Solution is split into three parts:
1. Modules
2. Infrastructure
3. WebHost
In the Modules part, I have five different Modules (e.g. Contacts, Core) which have their own Controllers, Models, ViewModels and Views.
Now I am trying to add a new Controller into the Contacts Module.
I have already added two Controllers earlier, which was no problem at all.
But after having changed lots of things (like adding and deleting dependencies, adding Models and Views, etc.) I receive the following error-message when trying to add a new Controller:
"There was an error running the selected code generator:
'The specified runtimeconfig.json [C:...\TestApplication\TestAppplication.Module.Contacts\bin\Debug\netcoreapp2.0\TestApplication.Module.Contacts.runtimeconfig.json] does not exist. "
I have checked the folder from the error message and there is no TestApplication.Module.Contacts.runtimeconfig.json.
But I have also checked the same folder in the original SimplCommerce solution, which I have copied parts from, and there is no such file either.
Where is the file from the error message specified?
And what can I do to solve this problem?
Thank you very much in advance!
This file is automatically generated by Visual Studio when you build the project. Interesting thins is that when I removed this file and added new Controller to my test project, this file appeared although I haven't built the solution. The issue looks like your project cannot be compiled.
Make sure that the project does not have any compile-time errors and try to rebuild it before you add the Controller.
I am trying to create a simple app that shows near real time emotions with a live web cam. I am using this guide:
https://www.microsoft.com/cognitive-services/en-us/emotion-api/documentation/emotion-api-how-to-topics/HowtoAnazlyzeVideo_Emotion
I've Downloaded the sample app:
https://github.com/Microsoft/Cognitive-Samples-VideoFrameAnalysis/
but I am unsure how I could make it run. the README says:
. Get API keys for the Vision APIs.
2. Open the sample in Visual Studio 2015, build and run the sample applications:
- For BasicConsoleSample, the Face API key is hard-coded directly in BasicConsoleSample/Program.cs.
- For LiveCameraSample, the keys should be entered into the Settings pane of the app. They will be persisted across sessions as user data.
I've got the API keys and inserted the Face API key to the Program.cs code and all of the API's into the settings.
It say's that it cannot find some namespaces as seen in the image:
Why does it say that the namespaces are not included in the Microsoft.ProjectOxford namespace ? Thanks
Edit: This was solved. After updating Nuget and all it still didn't work and the problem was that the pathname was too long.
What I did was downloading the project to desktop and than pressed extract files.
It created a folder with a long name and inside was another folder with a long name so the path was big.
Just put it in D or just extract here and not it will extract the folder inside the zip and not create another one with the folder inside.
You're seeing red squiggles because you're missing some dependent assemblies. These are provided via NuGet, so you should download it by right-clicking on the project, and selecting Manage NuGet packages.... The UI thereafter is hopefully self-explanatory.
Once the missing packages are pulled in from NuGet, you should be able to build+run the application. Once you run it, there should be UI presented where you'd enter the requisite key. The XAML for it is here.
I need to create a hierarchy of projects as well as projects access rights within MS-PWA.
the idea is to have a "Corporate Project" , of which underneath it resides our R&D, Finance, Marketing projects.
Restricitions off course should apply per project (some will have access to the root project - while others only access to their specific projects (sales people, marketing dept, etc.)
Is it possible to create such Hierarchy in MS-Project Server 2010 PWA?
Answer to your question is: No, you cannot insert project into another project using PWA, you cannot define cross project links using PWA. This can be done only using Project Pro.
And btw we also started with the same idea: to have a master project and manage security on a level of sub projects. That idea failed because it took too long to open the master - Project Pro opens all subproject together with master to update progress; another problem was high integration of the subprojects - too many cross project links.
One of reasons why you may want to create such structure is to see a progress of the whole company using data from departmental subprojects. Here is another problem - only Project Pro can update status of the master.
I would recommend to create a view(s) in PWA just to see all of the projects grouped somehow together - this will be easier and faster.
I am newbie in .net.Today I have created a sample. In that sample, I have stored data in database using N Tier architecture. If I want to use to Use BL or DAL method in other project(I mean BL method in UI or DAL method in BL), I found two ways.
First one is - Right click on project << Add Reference << Select Project in Project tab
Second one is - Right click on project << Add Reference << Select DLL in Browse tab
Could anyone tell me that is there any difference between both of them as both works same.Is DLL way better then Project Reference.If yes, then what is the benefits?
Thanks in advance.
Regards,
Mohit Kumar.
The correct way to do it is to add a project reference.
one of the most important differences is that a project reference is updated automatically when you change the referenced project.
for example- If you change your DAL method from GetEmployees() to GetAllEmployees() then you can use GetAllEmployees() immediately in your BL class, without compiling your DAL first.
You typically use the project reference when the reference is part of your solution. In this way the relevant latest code is always used.
You will reference an assembly when it is a third party component or not part of your solution. This is somewhat more static as you will be using the code at the version represented by the assembly. So any changes to the assembly will require you to physically overwrite the referenced assembly with the updated dll.
HTH
The differences between the 2 have already been answered, however just to add to that, I think the only difference between the 2 in VS is that if you add project reference it still adds a normal dll reference, except the reference is to the Debug location of the projects binaries (i.e. bin\debug\project.dll), so in essence you could probably just Add Reference in the same way and point straight to the latest compiled dll.
I have came across a very interesting difference between the two approaches, but in the context of having 2 projects, one shared among multiple developers and one private to each developer.
Let us say that the shared VS project is called projectS, and the private project is called projectP
Now if the objective is to have a centralized development, and the developer needs to access source definitions from both projectP and projectS so that pressing "F12" or "Go To Definition" in VS would bring complete definition, then we have to use the Project Reference and not the DLL reference, otherwise pressing F12 would bring the definition from the compiled "metadata" excluding all developer comments and other relevant data.
When adding a Project Reference to projectS from within projectP, VS will resolve references to the files included in projectS and referred to from projectP using the source definition in projectS, and not from "metadata" of the DLL associated with the referenced project (ProjectS.dll). Still, the projectS.dll will be included in the References folder and Development time, Execution time will be OK.
When adding a DLL reference, VS will resolve references from "metadata" stored in ProjectS.dll, even if the Referenced Project was added to the Solution of projectP as an "Existing Project". This would allow Execution time to be OK, however, Developer will not be able to press F12 and go to Source definition in projectS, he/she will have to do this manually from the solution search area.