I'm new at this.
I would like to use in my visual studio project calwidget dll.
I add the dll to my project and i was able to edit some properties but i don't know how to create/save/retrieve appointments (similar to the outlook style).
Create more than one calendar (in monocalendar.exe you can create more than one calendar)
I just found this thread
Free schedule/timetable GUI library for .NET
But unfortunetly wasn't helpful (probably because of my beginner level)
Can anyone please give me some advice or help me?
Thanks
To use the dll, you need to refer it first.
In Visual Studio 2012 (others too) go to:
Project-->Add Reference --> Click on Browse button and browse your DLL.
Once you refer to DLL, use Import statement in your code to refer to the DLL library.
To create more than one calander, You can create more than one intance of the class or usre one winform per user. It is something depend on your application.
As I promised a sample code, I have done a video on the same. I am not sure if you were able to follow my instructions above. So I put those all here. Click Here...
Related
can somebody explain what technique they used to do this? See the yellow area:
it looks like a totally new panel, programmed from scratch. I need to do the same: add custom areas to Windows Explorer, containing an advanced file manager. I'd like to know what technology this is (in particular, what COM interfaces do you need to implement? IDockingWindow?); where the documentation is (not just the reference but an introduction); and if there are source code samples. Thank you
This is NSE and it creates its own implementation of IShellView.
Hopefully someone can tell me what I am doing wrong here. I have a SharePoint 2010 workflow I am coding in Visual Studio, and I was trying to emulate what is being done here, but as soon as I hit this line:
PdfConverter pdfConverter = new PdfConverter();
My workflow errors out.
I have Phil's book (workflow's in action) which contains an old version of the winnovative dll in one of his code samples, and thinking that might be the issue, I downloaded the newest version from winnovative's site, updated the using line at the top from:
using Winnovative.WnvHtmlConvert;
to simply:
using Winnovative;
as per the developer documentation that came with this newer version, and still no luck. Is there something else I need to do that I'm missing when using this with SharePoint? When utilizing an XSL style sheet for some transforms I had to deploy the xsl to the templates via my project utilizing the sharepoint mapped folder from within Visual Studio. Is something similar required for the winnovative dll to be utilized as well, so that the functions within the dll can be accessed? Do I need to do regsvr32 on the sharepoint server to utilize (something that literally just occurred to me as I'm writing this post), or is adding the reference in visual studio and compiling my code enough? Sorry, not the world's greatest developer, so some insight would be HUGELY appreciated. Thank you in advance for your time.
I figured it out. Following the breadcrumbs of my questions, I found out the dll needed to be deployed to the GAC. Once I did that it worked. This has been a big learning experience, but at least now I know. Thanks for looking.
Does anyone know if the code editor used by VSTO IDE is available to use in my own projects?
I need to use a code editor in my project. I Googled to try to find one, but I found several third party solutions (pay or free) but they don't fit my needs.
In same way as Webbrowser control, is the "sourcecodeeditor" control of VSTO available to use as a project component?
In same way as Webbrowser control, is the "sourcecodeeditor" control of VSTO available to use as a project component?
[. . .]
Exists the class "MSVSTOSourceCodeEditor"? This is the question. Thanks
Unfortunately, no. Microsoft doesn't allow you to subclass its source code editor, nor do they provide a version for use in your own projects. As I mentioned before, they don't really want to encourage you to rewrite Visual Studio. They'd prefer that you bought it instead!
Have you considered creating a plug-in or extension for Visual Studio instead? It's a little bit different way of going about it, but it just might work for you. Your developers might find it more convenient since they won't have to switch back and forth between two programs.
If you're really set on rolling your own custom solution, probably the best thing to do is check the source code for some of the open-source, Visual Studio-style IDEs, and see how they've written the code editor:
MonoDevelop
SharpDevelop
KDevelop
Does VB.NET have anything similar to Java's JDK source code? When I used to work in Eclipse, I could right click and view the generated code, or "look under-the-hood" so to speak. I found this feature very helpful in understanding what was happening behind the scenes, and it helped me to write better, more simplified code.
I have so far been working with Visual Studio 2010's Object Browser, and I have also been looking at the generated designer files, but these often do not drill down far enough.
The best program to do this is called .NET Reflector and you can download it from here: http://www.red-gate.com/products/reflector/
It lets you see executables and DLL's under the hood
ScottGu has an old blog post about this:
http://weblogs.asp.net/scottgu/archive/2008/01/16/net-framework-library-source-code-now-available.aspx
You can also use the .NET Reflector to peek into the code for any .NET dll, but keep in mind it won't look like the code in Visual Studio :)
http://www.red-gate.com/products/reflector/
I have an ASP.NET VB.NET web project that references a VB.NET class library.
I add a new property to a class in the class library, then, from the web app, I expect to be able to use it immediately w/o errors and with full intellisense.
It used to work in 2008.
When I compile the class library, it becomes available but not until.
Was this nice feature taken away, perhaps in the interest of speed?
What's likely happening here is that the Class Library and ASP.Net applications are targeting different versions of the framework. If they are using incompatible versions of the framework then VB.Net will treat it as a file reference instead of a project reference and would give you the behavior you're seeing.
Right click on the project, select the Appilication Tab and make sure that both have the same value selected for Target Framework. That should fix the problem.
Visual Studio 2010 will officially launch on April 12, 2010. I'd say there's a good chance that problem will be fixed in it. Go see.
EDIT: corrected the date.