I just started to play around with EntityFramework. In VS2012 I can use the designer which nicely creates all the boilerplate code. However, I am now at a point where I wanted to start playing with overriding DbContext.Seed() to initialize the database with some data. While there is this quite easily done writing the DbContext myself, I was not able to find a way to do this from within the designer. It seems to be no option to modify the Designer created 'Context' class. The comment at the top of the file tells me, that all manually added code will be lost when the file is regenerated.
Am I missing something? Can someone please point me in the right direction. How can I do all the nice more advanced things and still continue to use the designer.
try to find a package in Nuget there will be a ready solution to connect. Read more here http://nugetmusthaves.com/Tag/POCO or search in google poco Nuget.
Related
I am creating a custom advanced PDF/HTML template. I switched between WYSIWYG editor and source code editor and maybe saved. So now my template no longer shows up properly when try to preview it.
Does anyone know how I can fix this so that the preview shows my
changes as I make them?
Can anyone suggest what I can use going
forward so this doesn't happen to me again (ex: an IDE where I can
preview before moving code into NetSuite)?
Also, I did not save my source code before editing it since I thought NS was just making a
copy of the code in the custom template. So if anyone knows where I can get a copy of the
original source code for the original template that may help as well.
Thanks in advance for any help.
To answer your third question, I am assuming you started from one of the standard Advanced PDF/HTML templates and hit customize? If so, you should be able to get the source code for the standard template the same way: hit customize, then switch to source code view.
Remember that NetSuite does warn you that once you switch to source code, switching back may not work for that template. I generally switch to source code mode and do all my work in that mode. I use a sample transaction to preview the changes, or hit the "preview" button in the template editor.
I am not aware of any editor that will let you preview this in WYSIWYG mode, but I use Visual Studio Code to edit the templates. They now also have a SuiteCloud integration plug in, but it's a bit buggy. WebStorm is probably ok, but is not free. There is also Eclipse which is free, but they are deprecating its NetSuite plug in, and the upload to account functions don't work anymore because of the security enhancement to authentication.
I'm trying to create simple custom command (added in TOOLS menu option) to open the tool bar with custom control in VS 2013 using VS Package project.
I'm following https://msdn.microsoft.com/en-us/library/bb165987.aspx this guide but not sure why it's not working.
When I click on it, it opens tool window but without content under it. I want to show the MyControl.cs or custom control content under it.
I've tried a lot to find it out on Google but no relevent article found for same.
I've notice when I created new VS Package, it created "MyControl.xaml" file which loading it's data properly. I deleted that file and created new user control "MyControl.cs" which is not loading data.
Not sure if it requires VSIX project or VS Package. Is there any other way to do this?
Nothing in vsix development is simple at first. Try using this tutorial. It's from a series you can find here.
For you to show custom tool window content you have to extend the ToolWindowPane class and override the Window property returning your content as a IWin32Window. The tutorial fully explains it, and very well I might add, and the series is excellent even though it targets vs2010.
I came across an article in MSDN that talks about Project Subtypes. It gave me an idea for a useful way to extend an existing project type, but I don't see anything that actually walks through the steps of creating a new subtype (is there a tool to get started, what classes do you need, how do you register it with Visual Studio, etc).
What little information I'm seeing is also leading me to believe that this extensibility point is really only used for code projects. I'm looking to extend the SSRS project type (available in BIDS or SSDT). Does anyone know if this is possible?
Any help would be appreciated.
I'd like to use the roles and membership ability of Orchard CMS to limit access to a staff portal in Orchard CMS. At present there doesn't look like there's an out of the box way to do it.
I've found numerous references to modules that should be able to help out but none seem to work.
Very Simple Permissions is a codeplex item suggested by some that has a dead link nowadays and doesn't seem to exist on codeplex.
Science Project: Quanta destroys my site everytime I try to install it with a missing dll issue, and not sure if its what I need anyways.
Does anyone have any guidance as to how to either: show/hide menu items based on roles using the standard menu system or advanced menu plugin
or
limit content visibility based on roles. If its a module fantastic, otherwise don't mind getting my hands dirty with some coding but a point in the right way to do this mvc style would be great. I'm going to presume I need to edit the controller for the menu module to check for current membership and adjust the view data accordingly. I'm moving away from webforms. slowly. Still getting my head around the framework.
Thanks for checking in.
For those who are still struggling with this, there's a module is called ContentPermissions which is available here:
gallery.orchardproject.net/List/Modules/Orchard.Module.Orchard.ContentPermissions
Once installed, you can then add the ContentPermissionsPart to the Content Type you want to secure.
Quanta really is what you want. You are probably missing one of its dependencies. Pete, the author, is also super-active on the CodePlex forums so if you ask there, you'll get an answer.
UPDATE: Orchard 1.5.1, the current version as I'm writing this update, supports content item permissions and menu trimming out of the box.
How do you handle improvements and added functionality to your existing SharePoint code?
Did you deploy your original code as a feature?
Do you create a new feature_V2 and deactivate the original?
What processes have you found that led to problems in the future?
I am specifically interested about WebParts, EventHandlers, and WorkFlows.
From what I can find, MS did not leave a "Best Practices" around updating existing code. (Actually, I'm not sure they left a "Practice" much less a "Best Practices")
You can see other questions around this topic:
how-to-upgrade-a-long-running-sharepoint-workflow-already-in-production
how-to-update-spitemeventreceiver-assembly-version-for-a-list-in-sharepoint
should-i-keep-solutions-and-features-in-a-1-1-ratio
What is your method?
I understand this question may be subjective, but I feel there is a large information gap surrounding this area of SharePoint development.
Thank you,
Keith
We always deploy custom code as features and solutions. When it is time to upgrade the existing code, all you have to do is stsadm -upgradesolution and everything works very nicely. I do not like the idea of having feature_v2 type features around...it makes it extremely difficult to keep track of the current version. I think you should only have one version of each feature in your production environment.
Leave the version control to your source control system.
I'm working at a shop that does a lot of SharePoint development. You want to deploy by feature with a solution package. You can easily upgrade your features as you go along and you will need to upgrade the solution package. This solution package can be created from a TFS Build server with WSPBuilder. As you along, the only thing left is to upgrade the solution and "Force" reactivate your feature to have the new feature of the feature.
Don't forget to do an IIS reset for any new code deployment that is done through the GAC. If you put anything inside like sitemaps and resources inside your 12, you will want to do a stsadm -o copyappbincontent.
If you deploy features that contain application files, you want to unload your application on ALL servers of the farm. It can easily be done by putting an App_Offline.htm at the root of every application on every machine.
When completed, remove App_Offline.htm (or rename it) and you are done. Your site is back online.