I have been playing around with wf4 for a while. I found various articles, videos(channel 9), blog posts and sites about wf4, but couldn't able to organize it in a proper way.
I look forward to create a Learning Catalog for
Windows Workflow 4 with VS 2010 and IIS 7 (without AppFabric )
Windows Workflow 4 with VS 2010 and IIS 7 (with AppFabric)
Please help me to create it...
post your answers
where to start?
what to learn first?
must learn topics - in the order of importance
publishing as WCF Service
hosting
The Windows Workflow Foundation Developer Center is a good place to start.
And if you want to take a course go here (shameless self plug)
I recommend a great book by Bruce Bukovics "Pro WF" (rewritten for WF4). Also check Microsoft's Ron Jacobs online video series.
Related
Is there a security resource / Blog post which demonstrates the goodness of ADFS 2.0(or general SSO) with the OWASP - Top 10 list of vulnerabilities?
There are few good resources for ASP .NET (the best one from Troy Hunt). But none of them speaks about ADFS 2.0. Is there any value add with ADFS 2.0 w.r.t to OWASP (Definitely there are !!) ? A constructive discussion will also be appreciated.
Your best bet is to talk to Gunnar Peterson (search for 1raindrop). He's the SSO/SAML go to guy. Troy is also good value and is definitely aligned with the Microsoft stack.
The Top 10 methodology is about what researchers found the year prior to publication (so OWASP Top 10 2007 was a summary of 2006 weaknesses). For better or worse, researchers don't often come across enterprise applications, stacks or core technologies, such as ADFS. Those that do are paid to look at them, and unfortunately, that usually entails a NDA.
A better approach is the one I'm adopting for the Application Security Verification Standard, and the OWASP Developer Guide - is to provide builders with building assistance, so a positive, verifiable set of steps you should take to protect yourself.
The Top 10 is a great education piece to get discussions started, but as I wrote in the introduction to the Top 10 2007, The Top 10 2007 (and all of them really) are not standards! Do not use them as such.
Jim Manico is working on a cheat sheet series with a zillion authors. If you have an interest in contributing to OWASP, maybe consider an ADFS or SSO cheat sheet?
thanks,
Andrew
How can I build a regular website using drupal? which module should I use for that?
That's a pretty generic question. You should check out http://drupal.org/start and work through their Getting Started documentation and tutorials. After that, you should have an easier time here or on their forums getting more specific information.
According to Drupal founder Dries Buytaert, Drupal is not for building regular websites but for building "ambitious digital experiences".
'Because Drupal evolved from a simple tool for hobbyists to a more powerful digital experience platform, many people believe that Drupal is now "for the enterprise". While I agree that Drupal is a great fit for the enterprise, I personally never loved that categorization. It's not just large organizations that use Drupal. Individuals, small startups, universities, museums and non-profits can be equally ambitious in what they'd like to accomplish and Drupal can be an incredible solution for them. Rather than using "for the enterprise", I thought "for ambitious digital experiences" was a good phrase to describe what people can build using Drupal. I say "digital experiences" because I don't want to confine this definition to traditional browser-based websites.'
At the 2017 DrupalCon Vienna, Buytaert stated: "Drupal is no longer for simple sites, but for sites with medium to high richness." Basically there are easier solutions for regular websites than maintaining Drupal securely in production on a web server.
Depending on how "regular" your "regular" website is, you might consider another platform.
All of Drupal's complexity and versatility, along with the time you spent learning them, would go to waste if you're just displaying a dozen or so static pages.
Is this is the case, Wordpress or Joomla might be better starting points.
I was just wondering if there were any changes in the Drupal 7 code that effect server load and speed for large sites.
Also, with 7 nearing beta release, should I wait to build the sites with Drupal 7? I'm a future kinda guy. I would like to be able to develop Drupal sites for a freelance business I am owner of, and would like to start soon. Is Drupal 7 accepted enough to be developing live, customer sites for? Security Issues?
Thanks
At this moment, D7 is not even ready for development yet, so I wouldn't even think of putting a D7 site live. There is no upgrade path between alpha versions, so any bugfix could break your site. Once the first beta release is out, you can start developing.
To see what's new in Drupal 7, see the September 2nd sildeshow on http://webchick.net/node/70.
Keep in mind that there is more than Drupal core; you'll probably also need contributed modules. Figure out which modules you will need and make sure that they are available for D7, or help the module maintainer port the module.
To make the choice, I would ask myself two questions:
Can you afford to wait until Drupal 7 is stable?
Do you really need D7 features?
If both answers are yes, start developing once beta1 is out and publish your site when it's running on 7.0-stable. Otherwise, use Drupal 6.
You should wait to pass to Drupal 7 until Drupal 7 will have an official release that is not a beta release, or a candidate release, and when the modules you are using are converted to Drupal 7. Even in this case, I would suggest to wait, as there are probably some bugs in the modules converted to Drupal 7 that will be discovered when users start to use them.
Although it has an enhanced object-oriented database API based on PHP Data Objects
and other database-specific optimizations; CMS wire is reporting the new version is somewhat slower. Other testers have reported the new version has traded performance for flexibility.
I highly recomend Drupal. Whitehouse.gov is Drupal as well as other federal agencies.
You should wait. There are few live Drupal 7 sites, but not many, and they're mostly done by Drupal experts, e.g. Drupal Gardens is running on Drupal 7, but that's made by the company of the guy who made Drupal itself. Drupal 7 is also a bit slower because optimization tends to fall pretty late in the development cycle.
That said, you can always try it out and go back to Drupal 6 if you run into roadblocks. For very simple sites, you may not have any problems.
I think it is better to upgrade D8 .it has ability to write module oop and twig theme.
I think it really boils down to what you want to do... Obviously if you need modules that aren't ready, then you wait. HOWEVER don't limit yourself to the modules that you are familiar with from Drupal6. Case in point: I am developing a rather simple site for a client using 7. At first I thought I would need to wait since Views Slideshow wasn't ready, but some looking around brought me to Field Slideshow, which did the job quite nicely - with the advantage that all the images were in one page (for future change and editing).
There are significant end user benefits to Drupal 7 in terms of usability and interface. This is nice if you deal with clients who are not overly computer savvy
We are building an ASP.NET website using C#.NET language and VSTS 2008.
Would you please let me know which are all the third-party tools those can help us in the complete SDLC of this project?
Thank you..
Regards,
Karina.
Try Microsoft Team Foundation Server. It will handle your source control, work item tracking, bug tracking, reports, and provide you with a Sharepoint project portal.
Phew! There's lots that you can use, basically a complete eco-system has been constructed around this.
Much depends on
the process you'll use to develop the software (waterfall? agile? a mix?)
where your people are (if you have remote folks, you'll need good collaboration)
how many you are (small projects won't need quite as much project tracking software)
the kind of project you're on (a large complex site might need a comprehensive database management system, a small one can just use free tools)
what metrics you need to report
how experienced your developers are
the kind of graphic design expertise you have and need
your budget!
And that's just off the top of my head.
More specifically, here's some third-party tools I've used successfully that I'd not consider starting a project of any size without:
A source code repository: Subversion is a good one, TFS is expensive but does the job
A continuous integration server: I prefer Hudson, others like CruiseControl.NET
A refactoring tool for software developers (Refactor!, Resharper)
A virtual machine system for hosting test systems on a server (I use VMWare)
For larger teams where you're using Agile methodologies and need to report progress, consider Scrumworks.
Putting it another way, I'd suggest that you budget at least $500 per developer for tools, add-ons and geegaws beyond Visual Studio.
At home I use:
tortoises - Source Control - http://tortoisesvn.tigris.org/
ankhsvn - VS Integration - http://ankhsvn.open.collab.net/
CruiseControl.Net - Continuous Integration - http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET
Screwturn wiki - wiki for knowledge sharing - http://www.screwturn.eu/
At work I use TFS.
I'm not sure where to start when it comes to load-testing ASP.NET applications. My team doesn't use VSTS so that option is out. Does anyone have any good suggestions or experience they can share?
I'ved used Microsoft's free Web Application Stress Tool. It lets you record a browsing session, then replay it using multiple clients.
It seems that Microsoft has pulled this application from the download center, but you can use this alternative download (it may require 7-Zip to unpack).
Red Gate Software has a product called ANTS that can be used to do this.
Click Here for product link
Using BrowserMob.com is quite cheap for what it provides. You can listen to an interview with the founder of Browser Mob on Startup Success Podcast #18.
You can use Grinder.
Its a nice Java Based Opensource tool, to load test webapps. Pretty lean as well.